You are viewing limited content. For full access, please sign in.

Question

Question

Workflow SDK Scrip Asistance

SDK
asked on February 23, 2016

two questions,

1 where can i find documentation for the Workflow SDK Scripting.  for example this.rasession.

2 how do i loop through a multivalue field from a starting entry in workflow so i can create a token with all the values concatenated together.

0 0

Replies

replied on February 23, 2016

You don't need to script to concatenate values in a multi-value token. Just use the indexing feature in the token editor and select "all values separated by...".

What sort of documentation are you looking for this.RASession? It's the connection the script makes to LF using the connection profile specified in the workflow.

0 0
replied on August 16, 2016

I am trying to do this very thing, but if I just want the values concatenated together and not separated by anything, I get an error - Invalid object name.

 

I have tried this workflow many times and it works perfectly if I have a comma, a space, whatever, but if I have All values separated by nothing, it errors out.

 

I was doing it with a space, but we have a lot of documents already filed similarly and I want the naming to be consistent so I can see if we have duplicates and a space in the file name will not correlate a duplicate with one already in there.

0 0
replied on August 16, 2016

Where are the values coming from? What does the formatted token look like?

"Invalid object name" usually indicates there is a character that's not allowed in document names. If I had to guess, "nothing" is translated to a new line character which is not supported in names.

0 0
replied on August 16, 2016

This is the piece of my workflow that updates the token.

This is the token in the Rename Entry activity

 

I just need the syntax for All values separated by nothing at all.

 

It interpreting that as a new line character makes sense. I have tried it with a semi-colon, comma, whatever and just deleted that from the brackets %(TPA#[]#), but that's invalid as well.

It otherwise works perfectly, I just need to not have a character separating my values.

0 0
replied on February 24, 2016

Thanks Miruna,

reading documentation i cannot seem to find instructions on methods for the SDK script.  for example when i try to use methods from the SDK such as LFDocument doc =, the intelisense does not fine LFDocument.  I have not done scripting in the Workflow arena in a while so i need a refresher.  General information regarding defining objects if this is different from he standard SDK.

0 0
replied on February 24, 2016

The SDK script activity uses RepositoryAccess (RA) instead of LFSO as of Workflow 9.1. So the methods would be the same as you see in the LF SDK documentation, it's got nothing specific to Workflow. LFDocument is a LFSO concept. In RA, you'd be working with a DocumentInfo.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.