Configuring User Request Workflow for Claims users

If you want to configure AX portal to use for external users you probably want to have a way to avoid you staff doing too much work managing the users requests. If you combine the claims capability of the portal with the workflow process then you can automate some of the work. Here is a quick video on configuring the user request workflow.

 

Cheers

Lachlan

5 responses to “Configuring User Request Workflow for Claims users

  1. Pingback: Azure Login Page Setup – Part 5 | OrganicAX·

  2. Hi Lachlan,
    I am able to create the workflow, but when I approve a user to go through the workflow they are able to authenticate, but then the workflow stops with an error: “Stopped (error): Cannot edit a record in Vendor request (VendRequstCompany). The record has never been selected.” Do you have any idea what I might have done wrong? Or have you seen this error before?

    Thanks!

    Like

    • Hi Dana
      I’ve seen similar issue. If it’s the same issue I’m thinking it could be a bug with the email sending. Is the error happening on the second step of the workflow if you have configured it to automatically create the use and then send them an email once they have been created?
      Cheers
      Lachlan

      Like

      • Yes its happening on the second step of the workflow. The only thing really different from your workflow and mine is that I am using it for a perspective vendor and not just a regular vendor (external). Do you know the KB# for this?

        Like

      • Hi Dana
        Have a look at the methods on the class UserRequestManager. There are three methods that potentially send an email. sendNewUserEmail, SendUserAliasEmail and sendACSAuthenticationEmail. There is a line in there for SysEmailSystemTable::sendMail. If you have a look in the sendNewUserEmail and sendUserAliasEmail the parameters ends with :
        mappings);
        about line 17 (sendNewUserEmail) or 20 (sendUserAliasEmail).
        these should be :
        mappings, ”, ”, true);
        Which you will see in the method sendACSAuthenticaitonEmail.

        I believe the hotfix KB to have a look at would be KB3071033 or raise a support ticket with Microsoft. If your code already has the code changed then it’s not the issue I’ve seen so raise a support ticket with Microsoft to help investigate further.

        Cheers
        Lachlan

        Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s