Hi,
Is this a user decision task? It would be more helpful if you posted the whole XML configuration for this task.
Let's say that it is a decision task, then you might be able to change the order by changing the the decision order in the XML. Or perhaps you tried this already. Eventually you might need to change the decision order in the workflow builder in backend - and this might be bigger job or at least you need to be very careful when you do it, since you need to pay attention to the following steps after the decision in the workflow.
Regards,
Karri
Hi Karri for your response. It is a user decision task. Here is the current XML snippet for this task. I did change the decision order in the XML, but this also seemed to have no effect. I will also ask our workflow person to look at the decision order in the workflow builder in backend. Thanks!
<ItemType name="uwl.task.webflow.decision.TS91000345" connector="WebFlowConnector" defaultView="TravelExpense" defaultAction="DisplayExpenseForm" executionMode="default"> <ItemTypeCriteria externalType="TS91000345" connector="WebFlowConnector"/> <CustomAttributes> <CustomAttributeSource id="WEBFLOW_CONTAINER" objectIdHolder="externalId" objectType="WebflowContainer" cacheValidity="final"> <Attribute name="TripNumber" type="string" displayName="Trip Number"/> <Attribute name="TravelerCostCenter" type="string" displayName="Cost Object"/> <Attribute name="EmployeeNumber" type="string" displayName="Employee Number"/> </CustomAttributeSource> </CustomAttributes> <Actions> <Action name="Approve" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no"> <Properties> <Property name="UserDecisionNote" value="true"/> <Property name="decisionKey" value="0001"/> <Property name="UserDecisionTitle" value="Enter a Rejection Reason"/> <Property name="display_order_priority" value="1"/> </Properties> <Descriptions default="Approve"/> </Action> <Action name="Return" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no"> <Properties> <Property name="UserDecisionNote" value="mandatory"/> <Property name="decisionKey" value="0002"/> <Property name="display_order_priority" value="2"/> </Properties> <Descriptions default="Return"/> </Action> <Action name="Reject" groupAction="yes" handler="UserDecisionHandler" returnToDetailViewAllowed="yes" launchInNewWindow="no"> <Properties> <Property name="UserDecisionNote" value="mandatory"/> <Property name="decisionKey" value="0003"/> <Property name="display_order_priority" value="3"/> </Properties> <Descriptions default="Reject"/> </Action> <Action reference="viewMemos"/> <Action reference="addMemo"/> <Action reference="DisplayExpenseForm"/> <Action name="launchSAPDetails" groupAction="" handler="SAPWebDynproABAPLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="no"> <Properties> <Property name="display_order_priority" value="uwlExcludeFromPreviewDetail"/> </Properties> <Descriptions default="launchSAPDetails"/> </Action> <Action name="followUp" groupAction="" handler="dummy" returnToDetailViewAllowed="yes" launchInNewWindow="no"> <Properties> <Property name="display_order_priority" value="uwlExcludeFromPreviewDetail"/> </Properties> <Descriptions default="followUp"/> </Action> </Actions> </ItemType>
Hi,
OK, I would expect that the order in XML does not really have any effect. I just hope that when you tested it, you refreshed the UWL cache and started a new workflow. The old work items might look the same since they were already in the "cache" and UWL doesn't use the new configuration for those, or whatever...
Perhaps the best way in any case is to change the order in backend. Then both backend and UWL will be the same.
Regards,
Karri
Thanks Karrie,
We did clear the cache, and as you suggested, we created a new item, but it appears this will need to be done on the backend. Thanks so much for your help.
Regards,
Cassy
