I created a process which will give access to a particular portal user permission to read and edit record. The portal user name is filled in the record page.
Process first triggers when a record is added then it read the portal user name in the record and assigns the access permissions. But the process is not giving access rights to the portal user.
Can any one help ?
Here are the screen shots : -
1. Process
2. After adding record and process completion, the access rights
It is necessary to grant the rights not to User role but for the Employee where you should indicate the value of the Borrower field http://prntscr.com/stoezu . It should be something like this [#Read Borrower.First item of resulting collection.Borrower#]
As for now you try to grant the rights to some role and the system cannot identify it.
I assigned the access role in process for employee. And the process works now.
But why can't we do for User role.
Even if it works with employee role. The borrower is not an employee. He/She is an end user who will fill the form. Why does it have to be assigned in Employee role.
The thing is that your process doesn't read the user role. It would be necessary to find the user's role first using additional read data elements and based on which role is found by, use it in Role parameter instead of Employee.
Our client has an issue that any change in object permissions is not being recorded in Audit Log, despite the fact that all the system settings for audit log are enabled. Is there anything missing besides system settings that need to be enabled in front-end?
To log changes in object permissions you need to make sure that "Log entity access rights management events" system setting is enabled. It's code is "UseAdminEntitySchemaOperationLog".
Please note that only changes applied in "Use record permissions" will be logged.
In order to log changes in column permissions there, you will have to turn on the "UseAdminEntitySchemaColumnLog" system setting.
As for the Operation Permissions changes, they are not logged in Audit Log.
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?
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?
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.
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:
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.
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.
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?
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)
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.
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.
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.
