Skip to main content
M
Mat16-Pearl
16-Pearl
December 8, 2022
Solved

How to use alias attribut in drawing / part?

  • December 8, 2022
  • 4 replies
  • 3584 views

Hi there,

 

I want to display a "released by" information on my drawing.

I created an alias attribute with this mapping:

 

 

roleBObject@wt.maturity.PromotionTarget~roleAObject^wt.maturity.PromotionNotice~primaryBusinessObject@wt.workflow.work.WorkItem~theWorkItemReference@wt.workflow.engine.WfVotingEventAudit~userRef^wt.org.WTPrincipal~name=name@wt.org.WTUser~fullName

 

The attribute works great so far and lists all User's Full Names, which were involved in the process.

Mat_0-1670510581637.png

 

The attribute should be shown as parameter "released_by_alias".

But in Creo no such parameter is listed.

 

What am I missing?

 

Best answer by TomU

Adding to what @HelesicPetr wrote, see this from CS248702:

 

TomU_0-1671047006283.png

 

4 replies

joe_morton
18-Opal
joe_morton18-Opal
18-Opal
December 12, 2022

I think you would need to add this as a new attribute in Creo, and probably make it part of your template files. You should also mark it as "designated".

 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
December 14, 2022

Hi @Mat 

It does not work that way as you think.

 

Calculated attribute is not populated to the drawing/model in creo automatically. It is not IBA attribute.

The calculated attribute value is processed when it is shown on Windchill page.

 

So in the Windchill it works perfectly everyone can see it but if you need it inside of drawing, you need normal IBA attribute and designated attribute in the creo drawing. 

 

Also you need some code to propagate the value from workflow to the drawing without checkout/in. after that the drawing revisualization is needed . 

 

Hope this information can help you.

 

PetrH

    T
    23-Emerald IV
    TomU23-Emerald IVAnswer
    23-Emerald IV
    December 14, 2022

    Adding to what @HelesicPetr wrote, see this from CS248702:

     

    TomU_0-1671047006283.png

     

      M
      Mat16-PearlAuthor
      16-Pearl
      December 15, 2022

      @TomU  and @HelesicPetr , Thanks for Your answers.

      @PTC: why, just why can't You provide this information like lifecycle state ( PTC_WM_LIFECYCLE_STATE ), Version  ( PTC_WM_VERSION ) or "modified by" ( PTC_WM_MODIFIED_BY )?

       

      To me, it is another basic feature missing in this overpriced software suite.

      But thanks god, that there is now an IOT interface.

        D
        18-Opal
        d_graham18-Opal
        18-Opal
        November 4, 2024

        @Mat ,

        What you are trying to do can be done but as has been mentioned not with an alias attribute.

        You are on the right track however to use the results of the voting to get the user's name.

         

        You can add code to your workflow that gets the user's name from the voting immediately after the vote occurs and then have this name pumped into the value of the CAD Doc Drawing's Windchill String attribute "RELEASED_BY_ALIAS" (or whatever you want to call it).  Your CAD Drawing just needs to have the same designated String parameter "RELEASED_BY_ALIAS".

         

        This creating/updating of the Windchill attribute can be done without iterating the CAD Doc if so desired.

         

        As @HelesicPetr mentioned, it's unrealistic to think PTC will think of and implement every customization all of us can think of.  Part of our job is to fill these voids on a case-by-case, as needed basis. That's the way I've always look at this as it's realistic.  Plus, writing customization is fun. 😁

          M
          Mat16-PearlAuthor
          16-Pearl
          December 17, 2024

          I was able to get a working solution for my problem, which I had at the first place ( displaying "approved by" on a drawing).

           

          I posted my solution here:

          https://community.ptc.com/t5/Windchill-Customization/Info-How-to-set-attribute-for-quot-released-by-quot-quot/m-p/988177

           

            Terms & ConditionsCookie settingsAccessibility statement