PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 10/19/2017 10:40 AM by  Bob WCHN
Landmark: Provisioning - Account Disabled Flag
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Bob WCHN
System Integ Spec IV
Private
Basic Member
(11 points)
Basic Member
Posts:5


Send Message:

--
10/19/2017 10:01 AM

    In ISA, on the Landmark Tab, there is an Account Disabled checkbox. I can't find a means of setting this flag with a Landmark Transaction Activity Node.

    I’ve tried setting the IsActorDisabled and AccountLockout.IsAccountDisabled Flags for the Actor and tried doing a ‘DisableActor’ update, but the checkbox still is unchecked.

    Then, I thought that maybe the flag is a reflection of the DELETEFLAG value (off for 0, on when the DeleteFlag has a non-zero value) in the GEN ACTOR Table, but neither the 'Delete Actor' or 'Delete' GEN ACTOR Functions made any difference.

     

    Is there a way to set the Account Disabled Flag from Process Flow?

    Thanks in advance.

    David Williams
    Private
    Private
    Veteran Member
    (3040 points)
    Veteran Member
    Posts:1024


    Send Message:

    --
    10/19/2017 10:05 AM
    You should be able to update with the ResourceUpdate node.
    David Williams
    Bob WCHN
    System Integ Spec IV
    Private
    Basic Member
    (11 points)
    Basic Member
    Posts:5


    Send Message:

    --
    10/19/2017 10:10 AM

    I forgot to put in my original Post that I also tried setting the IsDisabled Flag with the RM Node, that also was unsuccessful.

     

    Woozy
    Private
    Private
    Veteran Member
    (3478 points)
    Veteran Member
    Posts:704


    Send Message:

    --
    10/19/2017 10:20 AM
    Hi Bob,

    Just for clarification, you're trying to disable a LANDMARK actor, right? David is correct if you are trying to do this for LSF Pflow, but Landmark is different.

    In IPA to disable a Landmark actor, you need to use a Landmark node to call the "Disable Actor" action on the Gen/Actor business class:

    _dataArea="appProdline" & _module="person" & _objectName="Actor" & _actionName="DisableActor" & _actionOperator="NONE" & _actionType="SingleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & Actor="{actor id}"

    Enabling and actor works the same way:

    _dataArea="gen" & _module="person" & _objectName="Actor" & _actionName="EnableActor" & _actionOperator="NONE" & _actionType="SingleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & Actor="{actor id}"

    Note that this will only work if the update is called by a user that has security rights against Gen/Actor.

    Good Luck!
    Kelly
    Kelly Meade
    J. R. Simplot Company
    Boise, ID
    Bob WCHN
    System Integ Spec IV
    Private
    Basic Member
    (11 points)
    Basic Member
    Posts:5


    Send Message:

    --
    10/19/2017 10:40 AM

    I'm running the Process Flow from the Landmark side, but the Activity Nodes have access to both the Landmark and S3 systems.

    The Account I'm using can create and update Actors, Identities, etc.and do RM Updates.

    I've done the 'Disable Actor' to no avail.

    I'm assuming the Account Disabled flag (checkbox) is for the Actor, since it's seen on the Landmark Tab in ISA. I don't see any other 'Disabled' type fields in any of the GEN database Tables - ACTOR, AGENT, IDENTITY, IDENTITYACTOR, etc. I've looked through every function/option in the Landmark Transaction Activity Node and can't find anything else to try.

    Nothing I've tried has worked; even having our Infor Technical PM talk to some developers didn't yield anything positive.

    I'm still at a loss as to how to set this flag.

     

    You are not authorized to post a reply.