Hi @jbernardo,

We have something similar in place for numerous processes like that, but we’re doing them outside of the actual client.

On the Application Server we initially created a Script Poster with a config file that contains the URL you would post the XML files to. Something simple like a perform_mass_update on task where TEAM_ID = x, then TEAM_ID = y, then TEAM_ID = z. The process would loop through picking out all the Task ID’s it picks up in the Hierarchy Select.

We have since moved onto creating small Powershell scripts for more involved processes. For example where you would need a more involved script via SQL to obtain the initial data, this would capture what is required, and then process each record one at a time. Again this would result in the usual perform XML scripts being fired, but in a controlled manner.

These all sit on the main FSM Application Server, and we use a Task Scheduler for the processes to run at the times we desire. We find this is a great way to automate processes in the background, and would be something i’d do to execute what you have described above.

More than happy to try and help further if you want more information on this.

Best Regards

Ady

@jbernardo if you know the shipment ids you can import the data using Perform FSM MPMyou 

You could also use a scheduled process with a hierarchy select to find the shipments you want to post, make an update to the shipment then execute the process.  

@jbernardo if you know the shipment ids you can import the data using Perform FSM MPMyou 

You could also use a scheduled process with a hierarchy select to find the shipments you want to post, make an update to the shipment then execute the process.  

This would be more than perfect as we do have all the shipment ID’s ready as apart of our process

assuming it would be the “Perform_Post_Shipment” one?

what would i enter for “leave_extracted”

@jbernardo there is no need to set that.  you really only need to pass the shipment_id.