-
Scenario Role Event Rule maintenance
We have several situations where we need to apply a rule to every scenario role event. We would like to have an easier way to maintain this. Maybe have a Role Event Rule registration where we can register rules as defaults or a mass maintenance page.0 Shipped
-
Conduct workflow EmailTo field should be configurable
Conduct sets up ttWorkflowMessge-EmailTo field with the UserID value. This sets up the workflow in semi-anonymous mode. A workflow link generated using this method is high security risk. User can forward the workflow email to anyone on their netwo...0 Shipped
-
Inherit Validations plugin code - should bind on the current user's [boaUserID]
When validating or finishing at the Request Role level, the plugin doesn't bind on the current UserID. It does when you are validating at the task page level though. See attached. https://support.boaweb.com/hc/en-us/requests/128910 Shipped
-
Review Role Rejection to Roles with Dependency Complete = 0
BOAUnited Based upon Zendesk Request #3462. In the Reviewer Workbench, if a Review Role contains the same task as other Application Roles, it is possible to reject back to a Role where the dependency is not complete. Functionality should be inc... -
ttReviewRoleAggregate - Tables that contain case sensitive fields in primary key should be included
Please refer to Zen Desk 10914. The text tables in the content apps of dspConduct contain a case sensitive SPRAS field which is part of the Primary Key. The current functionality does not allow the insert of the data into ttReviewRoleAggregate due... -
ttRequestRoleFinish should have a Counter or a Sequence ID instead of relying on TimeStamp
I am trying to sort through some errors on ttRequestRoleFinish and I am finding that I cannot rely on the TimeStamp to show me the exact sequence of events. In this case, I have 7 records with the same exact TimeStamp. It would be more straight fo... -
Store the Rejecter in the tables together with the Rejection Reason
Currently, in dspConduct, the Rejection reason is being stored in some tables, but not who is actually rejecting the roles. When the customers want to know what happened we cannot extract that information from anywhere. It would be great to store...0 Shipped
-
Do not send Finish workflow emails to roles that have Auto Finish Role set to True in ttScenarioRole
Zen Desk #6812: We had a situation at SpinMaster where a Role is included in the Scenario but has Auto Finish Role set to True. The role is strictly there for a later role to reject against if they need changes made to their data. The Role still... -
Allow users to maintain some of their own settings.
In the cApps users could enable or disable workflow for themselves. Some users work in the system all day and use the request page as a work queue of tasks to complete while others depend on workflow. We have also had requests and questions regard...