Some new stuff in the Switch Configurator v 25

I see that you can now get the variables listed that is defined in a profile or process plan. That is great but it only works with profiles that you can select from the library.

First of all where is that library located.
Secondly could we get a property that let us set the path to the library by our own definition.
Would be very useful when you create profiles for a customer and have them in its own library.
Or a way the the configurator can see user defined libraries.

Just a wish…

Hi Jan, if you also use pdfToolbox with the desktop version and hot folder jobs, you would expect the library to be identical to the one in Switch. But that’s not the case at the moment.

As with the previous callas Switch configurators, all profiles available in the callas pdfToolbox app in Switch are located in the application folder under:

/cli/var/Profiles

Creating a new folder with other profiles would also load that new profiles.

You can see the used variable(s) of a profile under Properties in “List profile variables”.

Hi, OK I got it to see the profile from the Library but I can not get any variables.

This is how it looks if I select one of the default libraries

I do have variables in my process plan.

Thanks

Jan

I tried to reproduce this but was able to see also the variables of another process plan.

Could you maybe send us this process plan where the variables are not shown?

OK, I try a simple process plan and see if I can get it to work.

In this case it is an imposition with a lot of app.vars in the JavaScript.

I test a couple of other variants of variables and see if I can get it to work

Thanks

These app.vars in javascript variables like imposition runlists might be not supported for list variables, but that’s a good feature request.

Also the variables created with arbitrary checks or fixups might be not supported yet for list variables.

1 Like

I check what works and not. Since I have a process plan for the imposition I can ad a variable element in it and that might then work?

FYI, we will fix this issue in a future version. Our internal ticket number for this is CaBT 0022494

1 Like