Workflow Profile Hierarchies: Security Model | Application Security Roles v Workflow Security
Please share your practical advice to secure Workflow Profile Hierarchies per the two requirements below. Thank you. A. Workflow Profile Hierarchies: Admin v Builder/Business 0. 'Cube Root Workflow Profiles' | Admin and Business | Top Level Cube_suffix 1. 'Default/Child Workflow Profile Types' | Admin/Business 'Cube Root Workflow Profiles' 2. Admin 'Parent/Child Workflow Profile Types' | Admin/Business 'Cube Root Workflow Profiles' 3. Business 'Parent/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles B. Two Workflow Requirements: Admin v Builder/Business 1. Builder not allowed to see/create/edit: - Admin 'Cube Root Workflow Profiles' - 'Default/Child' and Admin 'Parent/Child Workflow Profile Types' | Admin 'Cube Root Workflow Profiles' - 'Default/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles' - Admin 'Parent/Child Workflow Profile Types' | Business 'Cube Root Workflow Profiles' 2. Admin/Builder allowed to see/create/edit: - Business 'Cube Root Workflow Profiles' -- Business 'Parent Workflow Profile Types': Review, Base Input, Parent Input -- Business 'Child Workflow Profile Types': Import, Forms, Journals C. Security Model: Application Security Roles + Workflow Security | Admin v Builder/Business 0. Security Groups: 'Admin Roles and Builder Roles' and Child Groups = 'Admin Roles' + 'Builder Roles' 1. Application Security Roles | Manage Workflow Profiles = 'Admin Roles and Builder Roles' 2. Workflow Security = 'Admin Roles' = Admin/Business 'Default Workflow Profile Types' 3.1. Workflow Security = 'Admin Roles' = Admin 'Cube Root Workflow Profiles' 3.2. Workflow Security = 'Admin Roles' = Admin 'Parent Workflow Profile Types' 4.1. Workflow Security = 'Builder Roles' = Business 'Cube Root Workflow Profiles' 4.2 Workflow Security = 'Builder Roles' = Business 'Parent Workflow Profile Types' D. Security Model Results: Admin v Builder/Business - 1 + 2 + 3 + 4 = Workflow Requirement 1 = Fail - 1 + 2 + 3 + 4 = Workflow Requirement 2 = Succeed Thank you, SMEs.
Get dependent entities on a review level workflow
Hi All, We have a parameter attached in the entity POV of all our cube views, and it works perfectly on base level. However, not in the review level workflow. Is there a way to include dependent entities in a review-level workflow via XFBR String? The entities in the review level are dependent, coming from the assigned entities in base level workflows underneath it. I have tried using objList = BRApi.Workflow.Metadata.GetDependentProfileEntities(si, profileKey) with no luck. Perhaps I am missing something. Bound list has been tested as well, and attaching the parameter in the POV of a cube view, only works in the base level workflows as well. When the workflow is a review, it will show a full list of entities that we do not want. Is there a way through the XFBR string and parameter in the member dialog? Appreciate all suggestions.
Cube views and Parameters
Hi All, I encounter this issue while opening a cube view from a form template in the Workflow. The same cube view opens without any issues directly but if you try opening the same via the workflow, it gives this error "Cube Views used for Forms cannot use parameters when referencing other cube views for Shared rows or columns. Unable to resolve substitution variable <paramtere_name>" .Some detail worth mentioning here is that we are using paramters for formatting and in one of those formatting parameters we are using another parameter. Has anyone encountered something like this and how did you overcome it. Thanks for your help 🙂 KR Arpit
Cube View Comments
Hello All, I have a cube view in which i am using on the Row Level a GetDataCell Function, example GetDataCell(Account1+ Account2): Name (Trade). on the column level i have a Comment using the V#Annotation:Name(Comments). however, on the GetDataCell the Comment is highlighted in Green. is there a way to be able to allow the user to write a comment on row that contains a GetDataCell function?
Audit History for Forms - CubeView drill down (v8.4)
I have drilled down to the bottom of both Origin and UD6 dimension which shows the data was loaded by corp accounting team. However, i cannot view Audit history for Forms - it continues to show as grey'd out. Does anyone know how to enable the audit history? thank you.
Make document attachment required on journal
Hi Everyone, Our business team would like to make it mandatory to attach a document to every journal entry. I know this can be done via a confirmation rule. However, one of our business partners googled this and AI returned the information in the screenshot below so they are questioning why we can't enable the setting referenced. We can't find this in any of the OneStream documentation nor see it when creating new workflow forms or journal templates. Is anyone familiar with this setting?
