There seems to be a new interface available for Object Permissions. However, some of our team sees the new interface when we click on the link in System Designer, while others are taken to the Advanced settings page. Is there a setting that configures which interface individuals see or is this part of beta testing?
Like
Hi,
Link "Object permission" will take you to the new interface, while "Advanced settings" in admin area are still leading to old interface. May be those users used different links?
Best regards,
Angela
Angela Reyes,
Using the Object permissions link takes me to the page in Advanced settings, not the new UI. This is true for all but one member of my team. The new functionality is not working reliably.
Janine White,
It is likely that internal feature that turns on this functionality is turned on only for that user. Tu turn that on for all users you can run the following SQL script:
DECLARE @featureCode varchar(max) = 'NewRightsManagementUI',
@featureId uniqueidentifier;
set @featureId = (select top 1 Id from Feature where Code = @featureCode);
IF @featureId is null
BEGIN
insert into Feature
(Name, Code)
values
(@featureCode, @featureCode);
set @featureId = (select top 1 Id from Feature where Code = @featureCode);
END;
delete from AdminUnitFeatureState where FeatureId = @featureId;
insert into AdminUnitFeatureState
(SysAdminUnitId, FeatureState, FeatureId)
values
('A29A3BA5-4B0D-DE11-9A51-005056C00008', 1, @featureId);
Best regards,
Dennis
Dennis Hudson,
How did that get turned on for only one user in our instance? I thought this was a core feature of bpm'online studio. This is not something that we have set. If it is being implemented universally for System Administrators, shouldn't there be a setting for it and/or be implemented for all or none based on the System Administrator role automatically? Will we have to do this every time there is a new System Administrator? This seems like a bug, not a feature, to me.
Janine White,
Unfortunately it is hard to tell how it could get turned on only for only one user as the changes in AdminUnitFeatureState are not logged by default. It may have happened because of some glitch in updating process, also this may have been set with a query in SQL executor. Nevertheless, the script I've sent earlier turns this feature on for All employees organisational role.
Best regards,
Dennis
Dennis Hudson,
Again, this was not set by anyone on my team. If there was a glitch in the upgrade, what else was missed? Should we roll back our instance 7.13 and have the 7.14 upgrade reapplied?
Janine White,
Dear Janine,
We've resolved this issue in terms of support incident. As described the issue was in incorrect feature activation. We've reactivated it for your application and it resolved the issue and all users are now able to see new access rights designer. These are SQL-queries that were used while resolving the issue:
delete from AdminUnitFeatureState where id = '0A27067D-5177-401D-9D17-9586B27F9EA8'
insert into AdminUnitFeatureState(FeatureId, SysAdminUnitId, FeatureState) values ((select id from Feature
where Code = 'NewRightsManagementUI'), 'A29A3BA5-4B0D-DE11-9A51-005056C00008', 1)
Best regards,
Oscar
I appreciate the fix. The interface is working for everyone now. However, as a Quality Engineer, I'm concerned about root cause. As I mentioned above, if the discrepancy was the result of a bad install, then there could be other issues that need to be resolved as well that we haven't realized. For example, the 7.14 upgrade also broke the main menu system. It is no longer ordered as specified in Workplace setup, rather it only appears alphabetically, which has been reported to support.
Janine White,
Without gathering logs and investigating the issue on the site it is hard to determine what exactly caused the issue, Please send email to support@bpmonline.com so the issue would be analyzed on your site based on your request as a support case.
Best regards,
Dennis
Dennis Hudson,
That's already been done and the fix applied in request #SR-0806825. The root cause provided was, "The reason of the issue was in deactivated feature called 'NewRightsManagementUI," but I'm not sure what that means other than it was a coding issue that was overlooked before publishing to production.