Currently Document status can be assigned single role or user but there is no way to configure multiple role or user assignment to document status.
Goal is to make document status to work as it is but for deciding access, instead of using Role and User on Document status, use Access tab (PA_DocumentStatusAccess) and consider role or user access configured there.
Should have migrated existing configuration of Role or user on PA_DocumentStatus and create records in PA_DocumentStatusAccess table. Then Role and User from PA_DocumentStatus should be dropped. New logic will not use Role and User on PA_DocumentStatus.
If no record in Access table then consider access is available to all Role considering current Window and form access to work as it is.
There is a migration issue with scripts 202106282230_IDEMPIERE-4836.sql
When the installation has PA_DocumentStatusAccess records configured and is using SYSTEM_NATIVE_SEQUENCE=Y
The script insert the record in AD_Sequence and in the same script tries to use the nextidfunc function.
This is a problem when SYSTEM_NATIVE_SEQUENCE=Y because the native sequence is not created.
Carlos Ruiz
December 23, 2021 at 8:21 AM
Thanks , you are right, fixed the code.
Deepak Pansheriya
December 23, 2021 at 7:23 AM
test case failed due to refactoring of code. The test case failed indicates scenario where access record has both User and Role set, But current user is not one who has assigned access. But login Role matching to access assigned role. In this case as per test case, it should not have access to dashboard as user and role combination should match..
But after refactoring, user getting access to dashboard if just Role matches.
Currently Document status can be assigned single role or user but there is no way to configure multiple role or user assignment to document status.
Goal is to make document status to work as it is but for deciding access, instead of using Role and User on Document status, use Access tab (PA_DocumentStatusAccess) and consider role or user access configured there.
Should have migrated existing configuration of Role or user on PA_DocumentStatus and create records in PA_DocumentStatusAccess table. Then Role and User from PA_DocumentStatus should be dropped. New logic will not use Role and User on PA_DocumentStatus.
If no record in Access table then consider access is available to all Role considering current Window and form access to work as it is.
xtab mattermost design discussion → https://mattermost.idempiere.org/idempiere/pl/ipw7ha1hh38j7c5xaf6e5i349a