You do not specify the user for ACS. Just the set of privileges (roles) that to use. The error you are getting might be an ftp error for the export destination. You can test the destination by going to the Destination in Admin. There is an icon at the top of the destination that looks like…. well… it has an arrow and clock in it.

Nope. Can’t do it. A search will only return latest released if there is one. You would have to go with a web app PX,

If it truly is a redline conflict then that means both change orders are trying to update the same BOM row. If the first change is allowed to go through then the second change would have an invalid state: updating a row that has been replaced. The redline conflict has to be resolved by the user.

ditto

Going to have to convert to something. I have switched to using tinylog.

9.3.6 now supports SAML communication so you can now integrate with Okta.

You will not be able to create that criteria or the other way around: user group having username. The underlying architecture is a relationship between user and user group.

Be careful with the update title block event. It sounds enticing but you can find yourself in a PX trigger explosion if someone ever does a mass update.

Same as in MS Project. It drives scheduling. Think of it as an arrow between tasks. If the rule on the arrow is Finish-Start then the current task is scheduled to start when the dependent task is scheduled to complete.

There is already a system notification “Change Orders – All Change Approvers Have Approved” that goes to the change analyst when all approvers at a step have approved. You can also create a dashboard that shows changes that are at step and not waiting for any more approvals.