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

Question

Question

Forms using a token for the path

Updated May 24, 2018
asked on May 17, 2018

I am trying to use a token in a save to repository task for the path that the entry should be saved to. Here is my configurations

Here is the value of the token "Existing_Job_Folder"

After the task runs, the entry shows up under just \Subcontracts

It completely ignores the value of the token. Why is this?

0 0

Replies

replied on May 17, 2018 • Show version history

Chad,

It should work, you just need to put the repository name at the start, i.e. if your repo name is TheRepo you would put \TheRepo\{/dataset/Existing_Job_Folder}\Subcontracts

OR if you already have the repo in your folder path variable, put the \ before it, like so \{/dataset/Existing_Job_Folder}\Subcontracts.

 

Rick

0 0
View 3 previous replies
replied on May 17, 2018

Hi Rick

The repository is optional

If I enter \ or REPOSITORYNAME\ that leads to the same place.

But what I am running into here is that if I enter tokens into the Path area they are ignored.

0 0
replied on May 18, 2018

Oh sorry, Chad, I thought that would work, it's working on mine.  I'm on version 10.1, don't know if that has anything to do with it or not.  After the run when you check the variables of the instance does it show it retained the value of 'Existing Job Folder?'

0 0
replied on May 18, 2018

Yes, I know I have done this before, maybe it is this exact build. It is the very last 10.2.1 build to be released. The last step in the process is save to repository and the variable is populated, but the entire variable value is empty in the final path saved. Only thing saved is the part I manually type in.

0 0
replied on May 21, 2018

I think I am missing a step here.  Is your Existing_Job_Folder a field on the form that is built with other information from the form?  Or is it hard-coded?  I am on 10.2.1 and I have a path built completely with tokens and it works fine.

TokenPathForms.png
TokenPathForms.png (3.24 KB)
Download
0 0
replied on May 21, 2018 • Show version history

It is a field populated by workflow, which gives the token it's value. The field is on the form but only because of a glitch where workflow can't see variables unless they exist on some form. It is just hidden so that the users can't muddle with it. But it is hidden with the class name .hidden so that the value is not ignored. The value is showing up perfectly fine in the variables view as shown in the screenshot on original post, it is just being ignored on save to repository.

 

Edit: I am going to try manually entering a default value and see if it works, since yours it working. But I can't see why it would matter where the data comes from, a token just needs to have a value set when it is called, regardless of where from.

0 0
replied on May 21, 2018

Once I tried to use variables in the field, it stopped working and like yours, only the hard-coded stuff was used.

0 0
replied on May 21, 2018

Gave this a try on 10.2.1 latest and got it to work successfully. I created the form below with single line fields for 4 folders, then used concatenate to create a folder path variable.

I used a save to repository task with the location 

{/dataset/Path__RO_}\Sub-folder

and the form saved to 

 

0 0
replied on May 24, 2018 • Show version history

Hi All

Thanks for your help on this. I joined the VAR webinar and got some assistance. It turned out it was an option in the save to repository I did not fully understand called "Save the submitted form with this process step".

This means that not only will the form assigned to this step be saved, but the values of the variables at this step will also be saved. So since the value of the variable was set right before the save to repository task, it was ignored anyways.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...