Move output file to predefined target

This functionality allows you to specify a target for your file output.

In this article you learn how to navigate the menus and define a target.

 

How to create a Job-Related Task

1) Go to Jobs (the so-called Jobcenter) in the SAWSConnector Suite.

2) Select Job-related rasks in the sub-menu.

3) And click on + (‘Add new task‘).

 

Another sub-menu opens where you can specify the basic conditions, for example when the task should start or what happens after the task is done. To learn more about this click on this link.

4) Click on the Task to do box and select ‘Move output file to predefined target‘.

And the Settings menu will open.

 

Settings

 

Conditions

Allows you to specify even more conditions and context for the follow-up job. You can create a condition by clicking on + (Add new condition).

To learn about this functionality in detail, please click on this LINK.

 

File name of the output file

Allows you to define the name of the final output file.

Please note: The name box allows to use placeholders. You can find a list of all placeholders via this LINK.

 

ZIP behavior

If you export more then one file the task will store them in a ZIP archive for easier management. This drop-down menu lets you select how the created ZIP archives should be handled.

You can either choose to leave the ZIP archives in their original states, archive or unpack them before the transfer or unpack them without the top folder (for example if there is only only folder inside it, making a top folder redundant).

 

Output path (relative to the project directory e.g.: ../CSLive/data/cache)

Allows you to directly determine an output path on your server.

It is recommended to always begin the path with: ‘../{your project name}/‘

 

Output DAM path (prioritized)

Here you can select the prioritized output directory for your DAM files inside the Contenserv Suite.

 

Run Example

To fully understand how you to select an output target it is best demonstrated with a case example.

My goal for this example is to give the job ‘Products‘ a target for its output.

 

1) I want to equip my ‘Products‘ job with the specific task.

 

2) Inside the ‘Products‘ job, go to the Job-related tasks and create one by clicking on + (Add new task).

 

3) For a Task to do I select ‘Move output file to predefined target‘.

 

The Settings menu opens.

4) Since I don’t have any more Conditions to set, I’ll just ignore them.

5) For a File name I take ‘Output-file‘ since this is just a case example.

6) I order the ZIP behavior to leave the files in their original states.

7) Since I am giving the taks an Output path for the DAM files, I just leave this box empty.

8) And for the prioritized Output DAM path I select ‘/Demo/Export/JSON Export‘ by just typing in the ID ‘14156‘.

 

9) I save my progress next to the tab tail below.

 

10) For the next step I have to define what should be exported first. So I go to Datamaps and select Mapping in the menu below.

12) By clicking on + (‘Add new formatting‘) I create a variety of formattings for the sole purpose of the export.

 

13) I create a few attribute collecting formats, like Product numbers, Labels or Descriptions.

14) However, since I wanted to demonstrate even further functionalities, I also create format for ‘PdmarticlestructureID‘ for the purpose of ‘Merge reference values‘.

15) With a click on the cogwheel symbol (the ‘Edit‘ button) I enter the sub-menu.

 

This is were it gets delicate:

16) For Reference attributes I select ‘Abbildungen (28)‘ and ‘Alternative Abbildungen (181)‘ (which is German for ‘Images‘ and ‘Alternative Images‘) so there is more to work with.

17) For the Format of the result value I choose ‘Loop head’ to create a […]

18) Then I click on the cogwheel symbol (the ‘Edit‘ button) again to edit the Loop head.

 

I am now inside the Loop head formatting:

19) As the Loop context I select ‘Loop for DAM references‘ (I will later define it precisely).

20) For a Unique name I choose ‘Media Loop‘ so I can easily track and identify it later.

21) As Format of the source value I ‘Create an array‘.

22) By clicking on the associated cogwheel symbols (the ‘Edit‘ buttons) or by selecting them in the drop-down menu in the left I enter the subsections for further editing.

 

Inside the Loop for DAM references:

23) I admire the beautiful designed menu yet feel a little overwhelmed by those long box descriptions … however:

24) I select the attributes I wish to be availablew in the loop cycle: ‘MamfileID‘, ‘FileName‘, ‘URL‘ and ‘ExportFileName‘.

25) The context profile for data, the attributes maintained at the reference itself and also the attributes according to which the lines are to be sorted before the loop pass have no relevance for this run example, so I just leave them be.

26) The Sorting direction will be ‘Ascending‘.

27) And as a Preset for local export I choose ‘AI Optimized (9)‘ – to make it easier for the Ursula AI to do its job.

28) And yes, I save my progress. Saving regularly is like the digital equivalent of brushing your teeth. Do it often!

 

Inside Create an array:

29) I have absolutely no idea what I am doing here. I fill some Keys with the Formatting ‘Loop value (Single value)‘, then go my merry way.

 

 

 

 

 

 

 

Was this article helpful?

0 0

How can we improve this article?

Please submit the reason for your vote so that we can improve the article.

Name

Email

Submit