Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Move input file after use

I'd like process to run and then move the input file. I'm able to set it to move the file, but it does so before running the input through the process.

The diagram above does not include my attempt at adding the "move" distribution- shown is the email distribution of the final output.

The process as built works correctly, but does not move the original input.

(Currently on Server 13.1)

Find more posts tagged with

English

Monarch

Accepted answers

All comments

Altair Forum User

This is my setup the does NOT work. Moves the file before using it in the process.

Altair Forum User

This is my setup the does NOT work. Moves the file before using it in the process.

One of the nuances of visual processes. You need to specify the data flow of when to move the input file. Data flow is determined by the solid gray lines. In the example below, my Input Distribution will occur after the Export Distribution is done. I tell the Input Distribution node what file(s) I want to move based on the dotted green line running from File Input(1) to Input Distribuion.

The built in help manual (accessed by the "Help" link in the upper right) provides a good explanation of what happens:

Instructions for process work flow building

-There are no mandatory graphical elements that must be used for work flow building.

-Starting work flow item is defined by absence of input connector. Process execution starts with the starting work flow item.

-Final work flow item is defined by absence of output connector. Process execution finishes on processing final work flow item.

-If there two or more starting items, execution starts synchronously and is divided in two parallel threads.

-You can fork work flow using connectors if you need to branch one thread of process execution into two or more parallel threads.

-Successful execution of work flow stage is defined by gray connector, unsuccessful execution of work flow stage is defined by red connector.

-By pop-up colorful arrows, the Process Designer gives prompts that some work flow items are available for connecting with the particular item and some work flow items cannot be connected with the given item.

-By pop-up single/double arrows, the Process Designer gives prompts that a particular work flow item can be connected with the single item only or with multiple items.

-For export operations, output work flow item can be an input item for subsequent work flow item.

Elements from the Input and Model groups do not define process work flow. Belonging to work flow is a benchmark why two types of connectors are used, namely:

-Solid line connectors — for connecting work flow items

-Dashed line connectors — for connecting non-work-flow items.

One more work flow (not data) indicator for a graphic element is availability of input and output pins of gray color on the element's icon (Pin image).

Connectors differ by color:

-Gray connector — implementation of work flow stage is successful

-Red connector — implementation of work flow stage leads to failure

Altair Forum User

One of the nuances of visual processes. You need to specify the data flow of when to move the input file. Data flow is determined by the solid gray lines. In the example below, my Input Distribution will occur after the Export Distribution is done. I tell the Input Distribution node what file(s) I want to move based on the dotted green line running from File Input(1) to Input Distribuion.
The built in help manual (accessed by the "Help" link in the upper right) provides a good explanation of what happens:
Instructions for process work flow building
-There are no mandatory graphical elements that must be used for work flow building.
-Starting work flow item is defined by absence of input connector. Process execution starts with the starting work flow item.
-Final work flow item is defined by absence of output connector. Process execution finishes on processing final work flow item.
-If there two or more starting items, execution starts synchronously and is divided in two parallel threads.
-You can fork work flow using connectors if you need to branch one thread of process execution into two or more parallel threads.
-Successful execution of work flow stage is defined by gray connector, unsuccessful execution of work flow stage is defined by red connector.
-By pop-up colorful arrows, the Process Designer gives prompts that some work flow items are available for connecting with the particular item and some work flow items cannot be connected with the given item.
-By pop-up single/double arrows, the Process Designer gives prompts that a particular work flow item can be connected with the single item only or with multiple items.
-For export operations, output work flow item can be an input item for subsequent work flow item.

Elements from the Input and Model groups do not define process work flow. Belonging to work flow is a benchmark why two types of connectors are used, namely:
-Solid line connectors — for connecting work flow items
-Dashed line connectors — for connecting non-work-flow items.
One more work flow (not data) indicator for a graphic element is availability of input and output pins of gray color on the element's icon (Pin image).
Connectors differ by color:
-Gray connector — implementation of work flow stage is successful
-Red connector — implementation of work flow stage leads to failure

Works! Thanks!

Altair Forum User

One of the nuances of visual processes. You need to specify the data flow of when to move the input file. Data flow is determined by the solid gray lines. In the example below, my Input Distribution will occur after the Export Distribution is done. I tell the Input Distribution node what file(s) I want to move based on the dotted green line running from File Input(1) to Input Distribuion.
The built in help manual (accessed by the "Help" link in the upper right) provides a good explanation of what happens:
Instructions for process work flow building
-There are no mandatory graphical elements that must be used for work flow building.
-Starting work flow item is defined by absence of input connector. Process execution starts with the starting work flow item.
-Final work flow item is defined by absence of output connector. Process execution finishes on processing final work flow item.
-If there two or more starting items, execution starts synchronously and is divided in two parallel threads.
-You can fork work flow using connectors if you need to branch one thread of process execution into two or more parallel threads.
-Successful execution of work flow stage is defined by gray connector, unsuccessful execution of work flow stage is defined by red connector.
-By pop-up colorful arrows, the Process Designer gives prompts that some work flow items are available for connecting with the particular item and some work flow items cannot be connected with the given item.
-By pop-up single/double arrows, the Process Designer gives prompts that a particular work flow item can be connected with the single item only or with multiple items.
-For export operations, output work flow item can be an input item for subsequent work flow item.

Elements from the Input and Model groups do not define process work flow. Belonging to work flow is a benchmark why two types of connectors are used, namely:
-Solid line connectors — for connecting work flow items
-Dashed line connectors — for connecting non-work-flow items.
One more work flow (not data) indicator for a graphic element is availability of input and output pins of gray color on the element's icon (Pin image).
Connectors differ by color:
-Gray connector — implementation of work flow stage is successful
-Red connector — implementation of work flow stage leads to failure

One follow up.

When I set the process trigger to Monitoring it runs correctly, but then continues to attempt running again and again after the input has been moved by the process from the monitored location.

cporthouse