Content Management and Capture

Hi,

we have a folder instance securized by a static role.
This role contains one principal (user group).

This folder instance is exported via FDM 5.5.9. During the import of this folder, the principal contained in role is not mapped as for all others objects.
An error occurs saying that the principal SID isn't found in the target environment.

The only way to import the folder instance is to recreate the static role but with empty role members.

It seems to be a program error. Ticket opened TS009905550.

Best regards

------------------------------
Yannick Martin
------------------------------

Hello,

As you have discovered, FDM does not handle principal mapping of members of a static role.  This is a known issue that is tracked by an internal enhancement request.  At this time, the workaround that you mentioned (or other similar workarounds, such as removing the static role from the exported object, or manually editing the deploy dataset by hand to remove members of the static role before import) is the way to get around this issue.

------------------------------
Paul MacAlpine
------------------------------

Original Message:
Sent: Thu July 07, 2022 05:37 AM
From: Yannick Martin
Subject: Issue in FDM 5.5 with role instances populated with principals

Hi,

we have a folder instance securized by a static role.
This role contains one principal (user group).

This folder instance is exported via FDM 5.5.9. During the import of this folder, the principal contained in role is not mapped as for all others objects.
An error occurs saying that the principal SID isn't found in the target environment.

The only way to import the folder instance is to recreate the static role but with empty role members.

It seems to be a program error. Ticket opened TS009905550.

Best regards

------------------------------
Yannick Martin
------------------------------

Wonderful, role-based access feature is introduced in 5.5.0 at the end of 2017, 4.5 years later, deployment of this feature is still not available...
Sometimes, I wonder how IBM tests its products...
And it is not an isolated case...

Meanwhile, business partners are doing their job to go through those bugs with customers. Thank you guys !

------------------------------
Florian KIEBEL
Practice Leader
Amexio
------------------------------

Original Message:
Sent: Thu July 14, 2022 09:02 PM
From: Paul MacAlpine
Subject: Issue in FDM 5.5 with role instances populated with principals

Hello,

As you have discovered, FDM does not handle principal mapping of members of a static role.  This is a known issue that is tracked by an internal enhancement request.  At this time, the workaround that you mentioned (or other similar workarounds, such as removing the static role from the exported object, or manually editing the deploy dataset by hand to remove members of the static role before import) is the way to get around this issue.

------------------------------
Paul MacAlpine

Original Message:
Sent: Thu July 07, 2022 05:37 AM
From: Yannick Martin
Subject: Issue in FDM 5.5 with role instances populated with principals

Hi,

we have a folder instance securized by a static role.
This role contains one principal (user group).

This folder instance is exported via FDM 5.5.9. During the import of this folder, the principal contained in role is not mapped as for all others objects.
An error occurs saying that the principal SID isn't found in the target environment.

The only way to import the folder instance is to recreate the static role but with empty role members.

It seems to be a program error. Ticket opened TS009905550.

Best regards

------------------------------
Yannick Martin
------------------------------