AnsweredAssumed Answered

AFX Fulfillment - How to use a Custom Parameter

Question asked by Andrea Saldamarco on May 4, 2017
Latest reply on Oct 27, 2017 by Sandeep Sharma

Like • Show 0 Likes0
Comment • 7

Hi,

I have implemented a custom request form in order to create an account on Active Directory. I need to use the AFX Custom Parameter, to change the UserName parameter of the form.

In oder to test the AFX Custom Parameter capability, I have added a SQL_Node in a Default AFX Fulfillment WF, with the following command:

select 'XXX1234' as AFXCUSTOM_CUSTOM_CUSTOMNAME from dual

In "Create an Account on an AD server" AFX capabilities I have implemented the following mapping:

mapping ${Custom.Customname}

When I submitted the request form the overead of parameter does not occur.

Is the above mentioned configuration correct ?

Thanks in advance

Kind regards

Andrea Saldamarco

No one else has this question

Outcomes

Tim Willemstein May 5, 2017 1:29 AM

Everything looks correct to me at first glance. Could you try to rename your parameter to something else AFX_CUSTOM_CUSTOM_NEWNAME or something like it.. wild guess that it has something to do with the CUSTOMNAME.

Actions

Andrea Saldamarco @ Tim Willemstein on May 5, 2017 5:45 AM

I try to rename AFX_CUSTOM_CUSTOM_NEWNAME but It not work

Actions

Boris Lekumovich

May 5, 2017 1:49 AM

I assume you are using some form, maybe a Register User type form.

See similar thread on that AFX Fulfillment - Change Parameter

I'm not sure about that, but it might be that when using a form, AFXCUSTOM prefix can't be used or the system ignores the AFXCUSTOM value and takes only the values which are coming from the form

Actions

Andrea Saldamarco @ Boris Lekumovich on May 5, 2017 5:29 AM

Hi Boris,

I use a Global Form. I have read the threadAFX Fulfillment - Change Parameter but I didn't find help

Is It a bug on my version?

Actions

Sandeep Sharma @ Boris Lekumovich on Oct 26, 2017 11:51 PM

Boris, just to confirm, AFX custom parameters DO NOT work with form provisioning command controls?

Actions

Boris Lekumovich

@ Sandeep Sharma on Oct 27, 2017 12:08 AM

I have never tried using variables with AFXCUSTOM prefix in a provisioning node.

I assume they will work, but there is no point/need in using them in a provisioning node.

The use case to use them (AFXCUSTOM variables), is when you want to pass workflow runtime calculated values to the connector when using AFX Fulfillment Handler

Actions

Sandeep Sharma @ Boris Lekumovich on Oct 27, 2017 3:45 AM

Boris I was not clear enough in my previous post.

I was actually referring to the following:-

Actions

7 Replies

Tim Willemstein May 5, 2017 1:29 AM
Mark Correct
Correct Answer
Everything looks correct to me at first glance. Could you try to rename your parameter to something else AFX_CUSTOM_CUSTOM_NEWNAME or something like it.. wild guess that it has something to do with the CUSTOMNAME.
Like • Show 0 Likes0
Actions
- Andrea Saldamarco @ Tim Willemstein on May 5, 2017 5:45 AM
  Mark Correct
  Correct Answer
  I try to rename AFX_CUSTOM_CUSTOM_NEWNAME but It not work
  Like • Show 0 Likes0
  Actions
Boris Lekumovich May 5, 2017 1:49 AM
Mark Correct
Correct Answer
I assume you are using some form, maybe a Register User type form.

See similar thread on that AFX Fulfillment - Change Parameter

I'm not sure about that, but it might be that when using a form, AFXCUSTOM prefix can't be used or the system ignores the AFXCUSTOM value and takes only the values which are coming from the form
Like • Show 0 Likes0
Actions
- Andrea Saldamarco @ Boris Lekumovich on May 5, 2017 5:29 AM
  Mark Correct
  Correct Answer
  Hi Boris,
  I use a Global Form. I have read the threadAFX Fulfillment - Change Parameter but I didn't find help
  Is It a bug on my version?
  Like • Show 0 Likes0
  Actions
- Sandeep Sharma @ Boris Lekumovich on Oct 26, 2017 11:51 PM
  Mark Correct
  Correct Answer
  Boris, just to confirm, AFX custom parameters DO NOT work with form provisioning command controls?
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Sandeep Sharma on Oct 27, 2017 12:08 AM
    Mark Correct
    Correct Answer
    I have never tried using variables with AFXCUSTOM prefix in a provisioning node.
    I assume they will work, but there is no point/need in using them in a provisioning node.
    
    The use case to use them (AFXCUSTOM variables), is when you want to pass workflow runtime calculated values to the connector when using AFX Fulfillment Handler
    Like • Show 0 Likes0
    Actions
    - Sandeep Sharma @ Boris Lekumovich on Oct 27, 2017 3:45 AM
      Mark Correct
      Correct Answer
      Boris I was not clear enough in my previous post.
      
      I was actually referring to the following:-
      
      Like • Show 0 Likes0
      Actions

AFX Fulfillment - How to use a Custom Parameter

Outcomes

Related Content

Recommended Content

Incoming Links