Hello,
We have a process for a few different customers that works well in an on-premise installation. It involves writing document metadata to a SQL table, using a form to uniquely identify a row based on two pieces of data, pull information into the form, correct data that wasn't right the first time, submit the form, and update the metadata on the original document as well as the update the row in the SQL table.
We're trying to implement this for our Cloud customers, but running into an issue. Typically, I would use the Search Repository activity on-prem to identify the document we need to correct using two field values. I only allow the workflow to proceed if only 1 entry is found, and am subsequently able to use the "Search Repository - First Result" token as the target of my Assign Field Values activity. However, I don't appear to have that option in Cloud workflow.
I was hoping I could retrieve an additional property from the Search Repository activity and use it with the Find Entry activity to maybe give myself a token that could identify the single document I want to target, but I'm not seeing anything that will do that. Anyone have an idea of what I could potentially try here?
Thanks!
Question
Question
Cloud Workflow - Assign Field Values to entry found via Search Repository activity
Replies
Solution appears to be using the For Each Entry activity - I couldn't find a way to use anything from the Search Repository activity other than For Each Entry, even if my Search Repository activity is intended to return just 1 result.
Had a thought after I made this post. I could potentially create a new field, map the entry ID to it when these original documents get created, and then retrieve that as an additional property in my Search Repository activity. Then, I can use a Find Entry activity to identify the original by the entry ID. Although I don't know how I would take that additional field retrieved in the Search Repository activity and use it as a token in a later activity. The "Result Count" seems to be the only token I can use later in the workflow from the Search Repository activity.
I am running across this issue where, in on-prem, you can address the Search Repository entries as Entries on which to perform subsequent Activities--in my case as target to 'Move Pages to'
I believe in Cloud you need to use For Each Entry, Assign Token of EntryID, and then Find Entry using the new token value which will provide an addressable "Entry" for subsequent activities