Can Fusion change enteredByID of an object?

[tibormolnar]

Hi All,

when Fusion creates a record (Project / Task / etc.) in Workfront, the enteredByID field on the new record will reflect the Workfront user that represents the Fusion automation (more precisely: the WF user who created the Oath application used by Fusion to connect to WF).

I wonder if there is any way for Fusion to create a WF record with a different enteredByID. For example, when Fusion processes a request and creates a new task (not by converting from the issue), I'd like the task to have the enteredByID matching enteredByID of the original request.

I tried mapping enteredByID in the Create Record module, and also tried changing the enteredByID via Update Record, but neither worked.

Thank you for any inputs.
Tibor

[Sven-iX]

Negative. Entered by is a system-set field (same as entryDate) and cannot be modified. 

[tibormolnar]

Thanks for the confirmation.

(It's a bit confusing that Fusion gives you the choice to set it in the Create/Update record modules.)

[Sven-iX]

Totally agree! 

[lgaertner]

Hello @tibormolnar,

I was already annoyed about this a few months ago too.

There is a workaround to let Fusion create a record as another user (a different enteredByID).

That approach requires a couple of steps which are not officially supported.

Using the Custom API Call module and making a GET request to the endpoint LOGIN, you can get a sessionID for any of your users.

login?username=<userEmail>

You will need to setup a connection to your Workfront instance for the HTTP app.

After that you can use the HTTP -> Make a request module, pass the sessionID as a header and create your record according to the Workfront API.

Regards

Lars

[tibormolnar]

Hi Lars,

thanks for the hint, it sounds interesting.

I get the first and last bit (i.e. obtaining the session ID, then creating the record with the custom API call with the session ID sent as header), I'm not sure I fully understand the middle step:

You will need to setup a connection to your Workfront instance for the HTTP app.

Can you please explain this a little further?

Do I need to have a separate Oauth App created in Workfront and a separate connection configured in Fusion?

Do I need one separately for each of the users on behalf of whom I want to create records? Or just 1 altogether, on top of the 1 that I already have for Fusion?

Thank you,

Tibor

[KristenS_WF]

Just a side note: I use a dummy account for much of my Fusion work (so that I can tell when Fusion took an action and not me personally).

Note--the FusionAutomation account (which has admin rights) and Fusion connection using it were both set up prior to our migration to the Adobe Admin Console.  I don't have access to the Console (it's managed by our IT dept.), so I'm not sure if this is still an option for new accounts/connections.

[tibormolnar]

That's exactly what I have: A separate WF user called Fusion automations, with sysadmin rights, used for creating the Fusion Connection. I wouldn't want all new records created by Fusion to be in my name, of course.