Hiding buttons so PigeonHole runs once per data card

EmailFacebookGoogle+LinkedInTwitterShare

We have a few customers who are using PigeonHole as middleware. Users click a button on the SOLIDWORKS Enterprise PDM data card, PigeonHole connects to an external database, reads the information, and populates several fields on the data card.

We have a former SyteLine customer who was updating “Description”, “Material”, and  “Treatment” on his  data card from this older system, but wanted his users to only be able to update the data card once. i.e. If later, someone changed the data card, he didn’t want users to accidentally click the button again changing the card values back to the old values.

This problem was solved with the data card’s control logic. The visibility of the macro button is determined by the “material” field on the data card. If there is a value, the button is hidden.
ControlLogic

 

(In this example, the maco button is hidden if “material” field has a value.)