We are under construction!

You may experience downtime, errors or visual oddities, but we anticipate all will be resolved by the end of the day.

Forum Discussion

Stulai's avatar
Stulai
New Contributor II
2 years ago

Simultaneously completed all WF forms for descendants.

Hello Everybody, Could you please help to get a solution how to complete all WF forms at once for all descendants. We already got the extensibility rule for this purpose but it's completing all WF...
Forms
Workflow
  • JackLacava's avatar
    JackLacava
    2 years ago

    Yeah sorry, the actual lists of forms are one level deeper, just change the For line adding .RequiredForms:

    For each formObj as XFFormSummaryInfo in objXFFormsForWorkflow.RequiredForms

    Intellisense is your friend...

RobertChatenier's avatar
RobertChatenier
New Contributor

JackLacava / Stulai ,

Can you help me with the declare of the WFProcess and WFStep?
We try to implement this rule our self but we cannot get the script into the "for each" loop.

Thanks in advance.

"For Each WFStep As String In WFEntities

For Each WFProc As String In WFProcess"

JackLacava's avatar
JackLacava
Honored Contributor
3 months ago

You know Workflow names, they look like "MyProfile.Import", right? That's what they are building in the line that goes Dim WorkFlowStep As String = WFStep & "." & WFProc - WFStep would be "MyProfile" and WFProc would be "Import". 

Now, in this case, they are populating WFStep with each string contained in a list called WFEntities, and WFProc with each string contained in a list called WFProcess. So before all this code, they probably have something like:

Dim WFEntities as New List(Of String)
WFEntities.Add("MyProfile")
WFEntities.Add("SomeOtherProfile") ' etc etc

Dim WFProcess as New List(Of String)
WFEntities.Add("Import")
WFEntities.Add("Forms") ' etc etc

Does that make sense ?

Looking at the name of their variables, they've probably used Entity names when naming their Profiles.