topic Re: Issues when transporting Composite Roles in Application Development and Automation Discussions

Issues when transporting Composite Roles

Former Member — Tue, 25 Jul 2006 06:15:54 GMT

Whenever we try to transport a Composite Role, it will comes with 2 options:

1. Also transport the single roles for the composite roles

2. Also transport the generate profiles of the roles

According to OSS 571276, if the first option is deselected, the composite role is transported without single roles.

My first question is:

Does that mean you will see empty single roles assigned under the Composite Role's Role Tab if you pick this option when you transport it?

My second question is:

If this option is selected, it will transport the single roles with it's updated changes to the target system. And, if one of the single roles are part of older requests and not fully tested, it will creates a situation of transporting single roles that are not fully tested yet to target system, isn't it?

My third question:

Which options of the above do you use when you transport a Composite Role?

I hope my questions are not confusing. The concern of these issues is prevent transporting singles roles that are still under testing to production.

Message was edited by: Annie Chan

Re: Issues when transporting Composite Roles

Former Member — Tue, 25 Jul 2006 21:59:23 GMT

Annie,

when transporting a composite role without its single roles, beahaviour depends on whether a single role with identical name is already present in the target system (e.g. from a previous transport).

If so, a user in the target system will be assigned this (possibly outdated) single role when having the composite role. If not, the user will not be assigned this particular single role.

The single roles should show up in the "roles" tab of the composite role in all cases.

If you select to transport all single roles with a composite role, they will be added to the transport request in all cases - even if they are already contained in a diffent transport request that has not been released. I.e. you need to ensure by yourself that the contained single roles are of sufficient quality to be transported.

I definitely would go for transporting a composite role incl. all its single roles. Otherwise the composite role might be incosistent and unusable in the target system. Ensure to only release your transport request if both composite role and all contained single roles are finalized and tested.

Regards,

Dominik

Re: Issues when transporting Composite Roles

Former Member — Wed, 26 Jul 2006 00:29:00 GMT

Hi Dominik,

I think I will have to go exclude the singles roles after reading your answers. Our composite roles have a huge list of single roles under them. If I were to transport the single roles, single roles that are still under testing stage will be transported. Since the single roles should show up in the "roles" tab of the composite role in all cases then there is no needs to actually re-transport them if I want them to be old state.

I realise you have solve my doubts

Thanks for your reply.

Message was edited by: Annie Chan

Re: Issues when transporting Composite Roles

Former Member — Wed, 26 Jul 2006 09:12:33 GMT

If you have created roles at a task level and want to merge them into a role at a role level... then there are a number of role merge programs available in the internet.

You can then continue with your "composite built role" but have the technical advantage of it being a single role.