well since you asked... 😃
1. Badge on Left Menu:
2. Charts on forms:
Charts currently require a query
Doesn’t work in all situations, eg we want to place a small, simple chart on a form
Can do a Reference Attribute and records, but this is quite “heavy” when you just want a simple chart
Currently we are using JavaScript charts to do this, it’s ok, but would prefer to keep all charts in Aware
Idea is to have an Aware chart that isn’t a query, it just gets generated based on attributes on the BO
For example, you can add say five attributes for the data points and the chart uses these for the data set
Alternatively maybe you can have one plaintext field that holds an array of data used in the chart, and we have to define it in a certain way with a rule eg [dogs:3;cats:1;fish:4]
This would be similar to how you add a Google Map to a form
3. Uploading and publishing new versions: (two new process rules)
This was briefly discussed at Conference, publishing is such a big thing:
It needs to be done late at night when no users are online (or else you kick users out and get errors such as can’t publish due to active processes), this means someone has to stay up late at night
The risk of error is MASSIVE. Publishing the wrong bsv over the top of another is a catastrophIc error, we have done it by accident (more than once), and isn’t helped that it is 1am when we do it (tired etc) and you are doing 15 each night.
Its a manual “one at a time” process. We can publish 15 BSVs a night, so it takes a long time. Login to dev server, download BSV. Login to PROD server, upload and publish.
How could this be improved?
I think with two PROCESS RULES we could build a solution that would please everyone. We can develop a few processes/functions to automate this process. What we would need:
An Aware process rule (function) to download the bsv and put it in a directory on the DEV server. Putting it on the dev server is really important, not on the machine where the remote config tool is. So a process like: EXPORT TEST BSV to ‘/directory/‘ and EXPORT CURRENT BSV to ‘/directory/‘ would be great. It would be good to be able to use tags here like EXPORT TEST BSV to ‘<<SystemSettings.BSVExportDir>>'
We could then build a seperate Aware bsv (lets call it PublishManager) that grabs these .bsv files and does manager approval rules and then move the bsv file to a special directory on the right PROD server (we could do an EXECUTE PROGRAM to move it with a bash script and SFTP, it would be great to have an Aware process rule to SFTP a file but I have no idea if that is possible - nice to have only )
From there we can create an Aware process on the PROD server that we can schedule to look in the directory and if there is a BSV in the directory then publish it. Basically an Aware rule like PUBLISH ‘/dir/filename.bsv’. it would be good to be able to use tags here too like PUBLISH ‘<<SystemSettings.BSVPublishDir>>‘ (could also it from a Document attribute if that is easier)
This process would log the results in some table with a status or error message. Eg Publish failed, success etc. That way we could monitor it and build rules to SMS us if a publish failed.
The ability to schedule the PUBLISH rule is really important. With servers in different timezones it needs to happen in the middle of the night. Also we can set it to be done right after our scheduled backup. And make it happen in a staggered way so 5 bsvs on the same server are not being published at the same time.
These two rules would be very helpful, it removes human error and in our case would save probably 3-5 hours a week. We just queue them up, approve them during the day and it happens at night while we sleep.
