ACS - read custom field on workflow resource via API | Community
Skip to main content
acc_acs
acc_acs
Level 3
September 21, 2021
Solved

ACS - read custom field on workflow resource via API

  • September 21, 2021
  • 1 reply
  • 2085 views

Hi There,

 

I need read a new custom field on workflow resource that I've just created, but I don't how know how I can read it via API.

 


I've been reading the documentation, but I can't found how can I to do it on workflow resource.

But I've tried a command and that I can read the fields on wkf resource, excepted my custom field that I created. Probably this command is not right.

 

The question: Is it possible, read a custom field on workflow resource via API?

If is possible, say me how, please. But if is not possible, I'd like to know if there is an another way to read it.

I will really appreciate for any help!

Paulo

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by SatheeskannaK

    @acc_acs,

     

    I don't think custom field created on workflow resource is not exposed to API.

     

    If you can provide more context on use case that you're trying to solve will help further to suggest something.

     

    Thanks!

    1 reply

    SatheeskannaK
    Community Advisor
    SatheeskannaKCommunity AdvisorAccepted solution
    Community Advisor
    September 22, 2021

    @acc_acs,

     

    I don't think custom field created on workflow resource is not exposed to API.

     

    If you can provide more context on use case that you're trying to solve will help further to suggest something.

     

    Thanks!

    Thanks, Sathees
      acc_acs
      acc_acsAuthor
      Level 3
      September 24, 2021

      @satheeskannak 

       

      I know the API can only read the Profile resource or the resources that are linked directly to the Profile.

      I tried to do this same process with the workflow resource. But it did not work.

       

      The scenario is as follows: I need to have the information in the workflow, the type of campaign purpose. For example, if it is Direct Marketing, Inquiry or any other.

       

      I need this information to integrate with another system that will send me this information. Only after verifying this information, I will be able to send the communication.

       

      I'm tentatively thinking about putting this information in the Label field or in the ID (name). I say this because I think that with the Endpoint (see the image)

       

      Example of Endpoint that I refered: "https://mc.adobe.io/<enviroment>/campaign/workflow/execution/WKF501/"

       

      With this Endpoing I can at least read the fields I mentioned above. I believe it would be a temporary solution until I think of a better one or Adobe implements that improvement. What do you think about this ideia? Let me know.

       

      Thank you so much for any help.

       

      Regards

      Paulo

        SatheeskannaK
        Community Advisor
        SatheeskannaKCommunity Advisor
        Community Advisor
        September 27, 2021

        Hi @acc_acs,

         

        Yes, i agree that temporary solution using label or name of the workflow makes sense based on what you can can execute against workflow resource using API.

         

        Thanks!

        Thanks, Sathees
          Terms & ConditionsAccessibility statement

          Loading footer...