[dspConduct] Final Finish Tables Execute After Rules in Registration Order not [PRIORITY] Order
Caroline St.John
Updated
Affects Versions
All released versions of dspConduct (ie 6.5.x and later)
Issue
Assemble/CranPort and Data Services Packages are not being run in the order specified in the [PRIORITY] field on the Task Final Finish Tables page.
The Final Finish plugin runs a query without an ORDER BY clause:
SELECT * FROM DataGarage.dbo.dgTargetSourceTableRule WHERE [Target] = 'dgSAP', [Source] = 'SAP', AND [Table] = 'KNVH'
This causes the After Rules to be ordered by an identity field named [Counter], which is not visible on the DSP page.
Workaround
For each final finish table, you must delete the Assemble and Data Services packages and re-add them in the order that you want them to run. The first package you add will run first, and the last package you add will run last.
To register an Assemble or Data Services package to download a table for the Final Finish process in dspConduct:
Click dspConduct > Design in the Navigation pane.
Click the Tasks icon for a category.
Click the Final Finish Tables icon for a main parent task (for example, Request (Address – General), as opposed to Request (Address – Telephone/Mobile)).
NOTE: It is recommended that tables not be registered to a child task.
Click Add to add the package that you want to run first.
Select CranPort or Data Services from the FINISH TYPE list box.
The number in the PRIORITY field does not matter. You must add the packages in the order in which you want them to run.
NOTE:The execution order of packages is by priority of the role (specified on the Roles page) to which the task is assigned, and then the order is specified by the order in which the package is added on the Task Final Finish Tables page.
Click Save; Vertical View displays.
Select a Collect source from the Source list box.
Select a Collect target from the Target list box.
Select the name of the table to download from the Table Name list box.
Select an option in the Run Rules After Download list box, if applicable.
NOTE: This option determines the Collect rules to run on a table after download, when a user with the Post role clicks Finish for the request on the Request Role page. Options are:
All – Run all of the rules: If multiple rules are registered to the table in Collect, dspConduct runs them on the table after download in the order the rules were added on the Table (Rule) page in Collect.
None – Do not run any rules: Though rules are registered to the table in Collect, dspConduct does not run those rules on the downloaded table.
NoParametersOnly – Run only Collect rules that do not contain input parameters, such as an Insert rule.
ParametersOnly – Run Collect rules that contain input parameters, such as an Update rule.
NOTE: The rule(s) must have already been registered and activated in Collect.
Affects Versions
All released versions of dspConduct (ie 6.5.x and later)
Issue
Assemble/CranPort and Data Services Packages are not being run in the order specified in the [PRIORITY] field on the Task Final Finish Tables page.
The Final Finish plugin runs a query without an ORDER BY clause:
This causes the After Rules to be ordered by an identity field named [Counter], which is not visible on the DSP page.
Workaround
For each final finish table, you must delete the Assemble and Data Services packages and re-add them in the order that you want them to run. The first package you add will run first, and the last package you add will run last.
To register an Assemble or Data Services package to download a table for the Final Finish process in dspConduct:
Click the Final Finish Tables icon for a main parent task (for example, Request (Address – General), as opposed to Request (Address – Telephone/Mobile)).
NOTE: It is recommended that tables not be registered to a child task.
Click Add to add the package that you want to run first.
The number in the PRIORITY field does not matter. You must add the packages in the order in which you want them to run.
NOTE:The execution order of packages is by priority of the role (specified on the Roles page) to which the task is assigned, and then the order is specified by the order in which the package is added on the Task Final Finish Tables page.
Select an option in the Run Rules After Download list box, if applicable.
NOTE: This option determines the Collect rules to run on a table after download, when a user with the Post role clicks Finish for the request on the Request Role page. Options are:
NOTE: The rule(s) must have already been registered and activated in Collect.