Skip to main content
1-Visitor
November 13, 2014
Solved

authorization for creating a promotion request ???

  • November 13, 2014
  • 1 reply
  • 2174 views

Hi everybody,

I do not succeed in creating a promotion request. New promotion request windows does open, but a pop-up 'you don't have autorization...' opens simultaneously...

Can someone provide a summary of required permissions / role / template to define?

By the way, I'm running Windchill Essential. I hope this causes no limitation regarding promotion request's ???

Many thanks in advance.

Best answer by ptc-2023985

Hi,

I could help myself in the meanwhile...

Hereafter a summary, just in case.

- permissions have to be defined at right context level : inside a organisation, regarding the right team

- promotion requests initialisation rules have to be dupicated at the organisation level also.

(maybe not mandatory, but it helps)

They should be actyivated and have to point to a writable default folder.

- remain relevant regarding groups, context, teams, etc...

Regards,

1 reply

17-Peridot
November 13, 2014

I have no idea if Windchill essentials limits the Promotion Request.

In PDMLink the following permission is set on the state "Open"

PromotionNotice.png

1-Visitor
November 14, 2014

Thanks,

Indeed no rule regarding PromotionNotice was present in the policies.

However WcAdmin has full rights to all WTobjects and he couln't promote neither.

I added a rule with full control on promotion notices for the designers group at organization level, but it still fails.

At least, its looks like beeing managed by the essential version, but other settings are missing or wrong, I guess.

I keep on fighting...

Regards,

ptc-20239851-VisitorAuthorAnswer
1-Visitor
November 19, 2014

Hi,

I could help myself in the meanwhile...

Hereafter a summary, just in case.

- permissions have to be defined at right context level : inside a organisation, regarding the right team

- promotion requests initialisation rules have to be dupicated at the organisation level also.

(maybe not mandatory, but it helps)

They should be actyivated and have to point to a writable default folder.

- remain relevant regarding groups, context, teams, etc...

Regards,