Is there an Attribute that we could add to a Model Header that would indicate the Database, e.g., Design or Production, so that users can instantly see which Database the model they are looking at is located in?
Best Reply
As far as I know, there is no standard attribute that provides this information automatically.
If I had this requirement, I would probably use an available standard model attribute and populate it with a scheduled script. The script could check the database name (or another database-specific identifier) and, depending on the result, write a value such as Design or Production into the model attribute. This attribute could then be displayed in the model header.
We used a similar approach in the past for object statuses: a scheduled script automatically updated an attribute, which was then shown accordingly in the model header.
I would avoid using macros for this purpose, as extensive use of macros can noticeably affect system performance.
3 Replies
Hi Mike,
I agree to Alexander, if you are using the "Model and Objects" environment only or use it for printouts.
Is it for designers or the business?
For the business I would provide the publishing functionality. Assuming you have two separate databases like Design and Production, which are both published, in "Published Content" the database name is displayed in the selection pull down menu in the header line of the window.
Regards
Klemens
Hi Mike,
your publishing process could write such an attribute to the model when you merge to the Publishing Database and before versioning the state there.
I have also seen a customer who changed the background colour of the models in the published database (also an operation in the publishing script).
Regards, M. Zschuckelt
Alexander Cherednichenko on
As far as I know, there is no standard attribute that provides this information automatically.
If I had this requirement, I would probably use an available standard model attribute and populate it with a scheduled script. The script could check the database name (or another database-specific identifier) and, depending on the result, write a value such as Design or Production into the model attribute. This attribute could then be displayed in the model header.
We used a similar approach in the past for object statuses: a scheduled script automatically updated an attribute, which was then shown accordingly in the model header.
I would avoid using macros for this purpose, as extensive use of macros can noticeably affect system performance.