I am looking for some explanations for the “Dynamic Workflow” property settings in the Call Workflow task. When should I use it?
The Dynamic Workflow property and fields allows you to pull the workflow name to execute from a task > field, instead of the workflow name being hard-coded in the workflow. The field must contain the workflow name to execute.
Excerpt from the “Application Building” (3.5.3, PDF) user guide:
Dynamic Workflow: The values of this field are used to dynamically define the name of the workflow that this task will launch. For the “Task with Workflow Name” drop-down list, select the task record that contains the workflow name. For the “Workflow Name Field”, select the field on the task record that contains the workflow name. This record field must contain the workflow name that you want to launch.
[Admin: To see other related posts, use the Workflow tag or Workflow Builder tag.]
In a Gantt section, the section is not honoring the associated report sort order.
The issue was caused by the dynamic ordering that was implemented by the project tasks’ internal tree set. The BO query comparison was performed by using the string form of the columns. Moving forward, we resolved an issue where the default Gantt sort ordering, and the sort ordering immediately after importing an MPP project file, did not correctly order by the sequence ID based on the Gantt section query configuration.
[Admin: This post is related to the 06.14.17 post about task date issues when importing MS Project (MPP) files. To see other related posts, use the Gantt tag.]
I have been trying to do an object migration (OM) import, but I am getting a validation error on one of the navigation collections contained in the OM package. It is not an error I have seen before, so I wondered if anyone could tell me what it meant? And how I can resolve it?
Which TRIRIGA Platform version are you using? I know we fixed an issue related to OM packages in our TRIRIGA 3.5.2 release, where certain navigation items were not exporting correctly, which may be related to you having problems importing the object. The following is the text from the TRIRIGA 3.5.2 release notes:
“Resolved object migration issues where Navigation Items may not export correctly if the Dynamic Label check box was selected and the Dynamic Label Query was not selected on the Navigation Item definition. (Tri-250723)”
[Admin: This post is related to the 05.19.16 post about inconsistent OM validation results. To see other related posts, use the Object Migration tag.]
If we add or remove users from the Workflow Agent settings on process servers (as per “best practices” to only have one “open” process server and others “restricted”), we have to restart all process servers for the change to take effect.
The 3.5.0 Administrator Console user guide [PDF] does not suggest that a restart is necessary and since this is the new “best practice”, it should be dynamic rather than require a system outage every time you make this change…
The problem lies in the task “Call triRFQResponseLineItem – Synchronous – Check Line Item Association” in the workflow “cstRFPResponse – triCompleteFinalHidden – Create triPurchaseOrder”. This task calls another workflow. But if you look at the properties for it, it has “Dynamic Workflow” checked, but no task selected for it. “Static Workflow” is not checked, but a workflow is selected for it. I’m not sure what the intention is, but if they fix this (by either checking “Static Workflow”, or selecting a task for “Dynamic Workflow”), the workflow should publish.