Skip to main content
Skip table of contents

Operation Update Profiling

The Update Profiling operation updates the Profiling located in the project with the specified ID.

Note:

The changes are updated only at runtime and are stored in a .runtime file. The .profiling file in the repository is not updated. For more information, see Using Runtime Configurations.

Example

Input

The adapter expects an XML document as input.

XML
<?xml version="1.0" encoding="UTF-8"?>
<Profiling active="true">
	<Id>f7adb9fe-93ea-4ca2-9023-1ebeca012931</Id>
	<Processes filterType="include">
		<Process path="Processes/dummy.wrf" />
		<Process path="Processes/Subprocesses/dummy_subprocess.wrf" />
	</Processes>
</Profiling>

The following elements have to be included in the input:

ElementAttributeDescription
Profilingactive

Possible values:

  • true: Activates process profiling for the current project.
  • false: Disables process profiling, identical with the behavior without the .profiling file within the corresponding project.
Id
UUID of the project where the profiling .profiling is located.
Processes

Parent element of single Process elements listed in it. (optional)

If no Processes is specified, the profiling with the filterType include refers to all processes of the current project.

ProcessesfilterType

Possible values:

  • include The following process list should be logged explicitly, all others are not logged.
  • exclude The following process list should be explicitly excluded from logging, all others will be logged.

Only one Processes element with a corresponding filterType can be specified.

Process
Single process for which profiling rules apply. Multiple declaration possible.
Processpath

Relative path within the corresponding repository project.

Possible values: String



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.