Related Tips & Info

Accessing IGA Workflow Administration Console

Fred Patterson
0 Likes

When I installed 3.7.3 in my lab I setup my default bootstrap account to be uaadmin via LDAP. I found out later as to the comments below that this is not recommended. It is best to use a bootstrap account that is not going to be collected or to associate it to a file and not LDAP.

If you are not seeing all of the tabs and only the dashboard, it is a rights issue, and you need to assign an account specific permission to workflow.

To access the Workflow Administration Console in 3.7.3 click on the little house icon and see if you can see Workflow Dashboard as well as the other tabs.

Below are a few images to help show what the workflow pages may look like in accessing them. 


Default Workflows:

Labels:

Education-Training
Knowledge Docs
Support Tip
Comment List
  •   in reply to Fred Patterson

    Hello Fred,

       That is correct.

    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    Micro Focus

  • in reply to stevewdj

    Thanks Steve.

    The terms "custom workflows" and "new advanced workflows" made me think that maybe there was some wiggle room as what is advanced VS what is a regular workflow. My new assumption now is that anything you would work on with the Workflow Builder is only for a dev environment currently and shouldn't be used in production, is that correct?

  •   in reply to Fred Patterson

    Hello Fred,

       You mean this statement:

    "
    IMPORTANT: The ability to edit custom workflows and create new advanced workflows using the Workflow Builder component of the Workflow Service is for preview and provided on an AS IS and AS AVAILABLE basis. We recommend that you do not use advanced workflows in your production environments. Workflow Service’s advanced capabilities will be supported and available for general use in a future release
    "

    i would only use it for testing in Dev at this time, as the note outlines.

    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    Micro Focus

  • in reply to stevewdj

    Thanks for the confirmation Steve!

    I noticed documentation is indicating limitations of workflows in production. Any advice on where the lines are drawn with supportability?


  •  

    Hello Fred,

    1) A user has to be assigned the Workflow Administration right within ID Gov to have full access to WF Console

    2) It is not best practice to have your bootstrap user when in LDAP be a collected user. They should be outside of the scope of the Identity Collector (or update the filter to exclude them) You would then set a collected user to be the Global and Workflow Administrator.

    Sincerely,
    Steven Williams
    Principal Enterprise Architect
    Micro Focus

Related
Recommended

Resources

Support
Documentation
Learning Services
CyberRes Academy
Partner Programs
Contact us
Compliance
Help
Company
Privacy Policy
Terms of Use
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Conduct
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.