Data Force Workflow status

Data Force Workflow status

carsten_maaß
Participant Participant
827 Views
4 Replies
Message 1 of 5

Data Force Workflow status

carsten_maaß
Participant
Participant

Hi Community,

 

is it possible to force items to next Workflow Status? We have some older database which still get datas. But now i need to "clean" like 7000 items which are in wrong Workflow-Status. Is there a way for me to force defined items to a special workflow status? Or do you have any other ideas how to clean it? They are in different Workflow states atm. For Example i attached 2 screenshots.

 

Thanks in advance

0 Likes
Accepted solutions (1)
828 Views
4 Replies
Replies (4)
Message 2 of 5

sven.dickmans
Autodesk
Autodesk

While there is no standard feature for such mass workflow transitions, you can use the REST API of Fusion Manage to transition multiple records easily. If you do not want to do the coding yourself, you can use my plm-utilities with the Implementation Helpers which automate various admin tasks. The utility Transition Records would be the right one for your purpose.

 

svendickmans_0-1740385325766.png

 

This set of utilities is based on node.js and allows for batch operations. The plm-utilities also include a tool to extract the configuration of a tenant and more.

 

svendickmans_1-1740385538589.png

 

If this is an option for you, I can rework the readme of this library with installation & setup instructions.

Message 3 of 5

carsten_maaß
Participant
Participant

Hi Sven,

thanks i installed it and was about to test. If i´m correct with your tool i only can change items from one status to a specific status? The Problem is, i would like to "only change items with deliverydate < 01.02.2025". hm....

0 Likes
Message 4 of 5

sven.dickmans
Autodesk
Autodesk
Accepted solution

This requires an adjustment of the filter condition in the file /admin-helpers/transition-records.js as shown in the screenshot below. While I did not test this example, this should work: Just add a 2nd filter condition that filters by the date field. Replace CREATION_DATE with the fieldId of deliverydate. When providing the filterValue, keep in mind that it has to be in format year/month/date. The comparator '19' will return entries 'earlier than or matching' the defined date.

        },{
            'fieldID'     : 'CREATION_DATE',
            'fieldTypeID' : 0,
            'filterType'  : { 'filterID' : 19 },
            'filterValue' : '2025/01/31'

svendickmans_0-1740465371794.png

 

Message 5 of 5

carsten_maaß
Participant
Participant

Works like a charm! and exactly what i need. Thank you very much.

Your the best 😉

0 Likes