Announcements

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

Rule in Event triggers (After save document) is conflicting with Vault Check in

tetsu.kanazawa
Participant

Rule in Event triggers (After save document) is conflicting with Vault Check in

tetsu.kanazawa
Participant
Participant

I created a rule to perform some routine checks, and one of the rules it executes is opening a Form, it includes it in the event triggers (after save document), but as I use vault (basic), when I click on Check in, it It asks if I want to save, when I click on YES it opens the FORM, and when I click on CLOSE the process ends, that is, it doesn't open the Check In window, it stays in this loop, when I put it as (before save document) it works, but interferes with other tasks

 

note, even if I perform the manual Save, before clicking on CHECK IN, when clicking on CHECK IN it requests the SAVE.

 

Inventor 2020

Vault Basic 2020

 

 

0 Likes
Reply
222 Views
3 Replies
Replies (3)

AndrewHumiston
Advocate
Advocate

good morning!

 

First and foremost, you might have to find a new trigger, when you are saving and use an iLogic trigger that takes place after save and a from is involved then it will abort the check in (Just tested it with Vault Professional). With that being said, we use a rule that updates the sheet metal extents parameters and i have no issue with that (although its set to before save). 

 

would you try disabling the user form and running the rule? I'm wondering when the form pops up if it exits the 'check in save' routine for the vault? What is the value of the user form? I'm curious as it pops after a save so anything you do would 'dirty' the file and require another save, this seems like you might be creating a loop that perpetually saves then dirties the file.

 

What actions are being done after a save?

 

i hope this helps!

0 Likes

tetsu.kanazawa
Participant
Participant

The rule executes other small rules. One thing I did was to include some fields in the Custom iProperties, as they did not exist in iProperties or did not meet my needs for what I was going to do (create lists, export BOM, etc.). To satisfy your curiosity, the rules are: include the Area in the custom, include the “blank” of the part, include the material, alert the file type, check if the part number is the same as the file name, open the Form.

I understand the Loop, but during the modeling of the part or assembly, the user saves several times, meaning that by the time they reach the final save, they have probably already corrected or filled out the created Form. I had made the Triggers Before save, but I had a problem during the SAVE AS, where clicking on SAVE AS opened the FORM, and if it was changed, it altered the original part and still copied it to the next part, causing the user to lose the original part’s fillings. This can be corrected by alerting the user, but I wanted to avoid this possibility, as users are people, and people forget or make mistakes.

 

Screenshot_3 is the Form

 

@AndrewHumiston 

0 Likes

AndrewHumiston
Advocate
Advocate

An idea might be to use the 'on open' trigger. that way when the file is opened it would fire the rule.

 

I'm not familiar with vault basic. does it offer the ability to 'copy design'? This is a much more robust way to copy files, save as only copies the file that you are working on, and nothing that is 'associated' with that file.

 

i found this in the help menu, this might alleviate the 'save as' workflow you where describing.

 

https://help.autodesk.com/view/VAULT/2022/ENU/?guid=GUID-A8071CF9-F5F6-457A-B335-0E81B7F60E6E

 

 

0 Likes