Forum Discussion

sfilho's avatar
sfilho
New Contributor III
3 years ago

Getting the Workflow Profile Text1 attribute value using BRApi

I am trying to get the Text1 field value using a Business Rule and put this value in a cube view that is being used as Form. Does anyone have done this before? Is it possible to get the Text1 value...
Admin
  • sfilho's avatar
    sfilho
    3 years ago

    Yes it is ugly. I could not get this piece working properly:

    GetAttributeValue(BRApi.Finance.Scenario.GetScenarioType(si, args.SubstVarSourceInfo.WFScenario.DimId).Id

    I replaced with:

     

    Dim wfClusterPK As WorkflowUnitClusterPk = si.WorkflowClusterPk

     

    Dim wfScenarioTypeID As Integer = BRApi.Workflow.General.GetScenarioTypeId(si, wfClusterPK)

     

    Dim sVarStep2 As String = BRApi.Workflow.Metadata.GetParent(si, args.SubstVarSourceInfo.WorkflowUnitInfo.ProfileName).GetAttributeValue(wfScenarioTypeID, 18000)

    It brought the correctly value.

     

db_pdx's avatar
db_pdx
Valued Contributor

Hi sfilho:

Are you only using the Text1 as a POV selection in the cube view?  If so, you can reference it directly in the Cube View as |WFText1|, no BR required.  Let us know if that satisfies your requirements.

Cheers    -DB

sfilho's avatar
sfilho
New Contributor III
3 years ago

Helllo There, The Text1 field that I am using is at the level highlighted in red. Is not at the ".Forms" level.

Thank you for the help

 

  • db_pdx's avatar
    db_pdx
    Valued Contributor
    3 years ago

    Add it to the Forms level?

    • sfilho's avatar
      sfilho
      New Contributor III
      3 years ago

      😊That's what I said. Then I heard "Well than we will have to remember to update that field in every .Forms profile we create" then  I said "Yes you might want to remember that". Anyways this is stored somewhere in the database in a table. I would think that a method to get that information should exist right?

      • db_pdx's avatar
        db_pdx
        Valued Contributor
        3 years ago

        At least for our implementation we don't have too many distinct Form Templates so it is really only an initial setup thing in my opinion.  Also, a reminder: you should be adding more Forms to the Template.  Not creating new Templates for singular Forms.  This way any new form they add to the Form Template will already benefit from the metadata you are adding to that step.

        Back to your original question, yes, we can get at it; it is just ugly.  Assuming usage in an XFBR String Business Rule

        myString = BRApi.Workflow.Metadata.GetParent(si, args.SubstVarSourceInfo.WorkflowUnitInfo.ProfileName).GetAttributeValue(BRApi.Finance.Scenario.GetScenarioType(si, args.SubstVarSourceInfo.WFScenario.DimId).Id, 18000)

        Where the Attribute Index is:

        Text1 = 18000, Text2 = 20000, Text3 = 22000, Text4 = 24000