Process Developer Resource | Description |
---|---|
.image | When you save a process, a screenshot of your process is automatically saved as multiple images in a folder named .image. When you deploy, Process Console uses these images to display the Detail Graph View of the process. Without this information, a default process graph is displayed that may not match the look of your process. We recommend that you preserve the .image folder and all files in it. |
.archive_settings.properties | In the BPR Export wizard, you can make selections for the Web Service URL and other settings. These settings are stored in .archive_settings.properties. During subsequent uses of the BPR Export wizard in a project, the Process Developer uses information in this file. |
merge_mappings.xml | (Human Tasks) When you create a task form for a People activity, you can map task input data to output data fields so that a consolidated list of fields are displayed in the form for the input and output fields that could be merged. The input-output mapping is stored in this XML file. Typically a mapping is created only through a one-time use; however, we recommend you preserve this file with your project. |
.BPR, .BPRD,.project, .classpath | Business process archive files (BPRs) can be regenerated by using the Export wizard. However, if preserved, they are easily shared among team members because they are self-contained. An Ant file that you generate (.BPRD file), on the other hand, can contain a Web URL that points to a local host and port that other team members may need to modify. The Eclipse files created, including .project and .classpath (if used), should be preserved with your project. |