Salesforce

Warning Messages (Magic xpi 4.6)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Warning Messages (Checker) (Magic xpi 4.6)

Below is a list of Warning-type errors that are displayed by the Checker:

Code

Description

100

Project must include at least one trigger or Autostart flow.

101

More than one external trigger type with the same name.

102

There are no flows defined for the Business Process.

104

Defined Server does not exist in the Server Repository.

106

The flow is empty.

107

Trigger has been defined on an empty flow.

108

Autostart property is set on a flow with a defined trigger.

109

Empty flow has been invoked.

110

The referenced flow does not exist.

111

The flow has more then one Save Point step.

112

The flow has more than one Wait for Completion step.

113

Parallel threads with no Wait for Completion step may cause integrity problems during recovery.

114

No parallel or stand-alone siblings for the Wait for Completion step.

115

No Save Point components defined for the flow recovery policy.

116

Condition required for multiple linear branches on the same level.

117

Incomplete or missing Email settings in the project’s properties.

118

Publish Event utility must be defined for this Subscribe utility.

119

Unlock utility must be defined for this Lock utility.

120

Post Event utility must be defined for this Wait for Event utility.

121

Variable was selected more than once in the invoked flow.

122

Mismatch in Format or Picture definition.

Note:

This error occurs when a picture used in a mapped element is different than the default for this type. It notifies you of potential runtime errors when the mismatch was accidental or when the permitted picture size was exceeded (for example, more than 18).

123

Data Mapper has no mapping connections.

124

Mismatch in Data Mapper connection type.

125

Data Mapper called an empty flow.

126

Data Mapper called a flow that does not exist.

127

XML position forwarding without a call flow definition.

128

Invalid XML position forwarding mapping.

129

Incomplete service component definition.

130

Variable does not exist.

131

Environment variable does not exist.

132

Web service Fault is not mapped to a variable.

133

UDS index does not exist.

134

ODS scope was changed.

135

Invalid Data Mapper node path definition.

137

Incomplete or missing enablement definition in project properties.

138

Incomplete or missing resource definition in flow DB Transaction definition.

139

Conversion Table entry does not exist.

141

Defined flow errors do not exist in the Errors Repository.

142

Disabled flow called.

143

Inactive flow called.

144

Defined Step does not exist.

Reference
Attachment 
Attachment