cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Condition script on save/modify (without workflow)

Condition script on save/modify (without workflow)

Currently it is not possible to have complex conditions before save/modify where scripting (and perhaps external API) is involved when there is no need for an approval workflow (where conditions can be applied).

E.g.:  Check if ERP number exists in the ERP system, have at least x items of type y linked in relationships, allow only BOM items of a specific type, if user choose attribute value x then...else..., or other more complex logic, ...

It should also be necessary to give meaningful feedback to the user (same way as workflow condition scripts).

 

A workaround would be to allow to give feedback to the user in the current action scripts with a return message, now we can only raise a 'general exception'.

 

 

4 Comments
Status changed to: Under Review

Hi @AndriesMuylaert ,

 

If I understand it correctly, you are looking for triggering scripts only on certain conditions? I.e. if certain fields have been modified, then an OnEdit script is triggered?

 

Thanks in advance for the feedback, appreciate it.

 

Giliar Perez
Product Owner - Fusion Lifecycle
Autodesk Canada Co.

AndriesMuylaert
Enthusiast

Hi @giliar.defriesperez ,

 

No, not really, in my particular case we want to check a condition that only 'Parts and Boms' with root classification type "BOM" are added to the Bill of Material Tab of a workspace. This workspace has no workflow (revision controlled) where we can check conditions like this and action scripts are not meant for this type of condition check, there are also not able to give meaningful feedback to the user (only raise 'general error'). 

 

A 'condition script' (not action) where we can check complex conditions AND give meaningful feedback to the user BEFORE the save occurs would solve multiple issues:

  • Complex conditions can be checked with logic (not only on 1 field but across different fields and Tabs where default validations rules are insufficient)
  • In the condition you could even call external API's (like e.g. check in ERP system if Part Number exists)
  • Meaningful feedback can be given to the user (similar to workflow condition scripts)
  • Occurs BEFORE Save (Action script on Save/Edit is sometimes too late)

There is no need for modifying fields in this condition script, so this is very similar to workflow condition scripts but without workflow of course and before save.

 

I hope this explains the use case.

Status changed to: Under Review

@AndriesMuylaert ,

 

Thanks, that explains it. I'll file an internal ticket. For now, I'm going to keep this in Under Review to gather more comments and feedback from the community, and re-assess at a later time based on the feedback. I appreciate taking the time to file the idea - thank you.

 

Giliar Perez
Product Owner - Fusion Lifecycle
Autodesk Canada Co.

amitabh_verma
Autodesk
Status changed to: Gathering Support
 

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea