<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tg/onlinemanual/000012" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">formal to actual definitions</Title>
		<Keyword><Level1>formal identification</Level1>
		</Keyword>
		<Keyword><Level1>actual identification</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>The formal identification of a business process is a reference to a specific version of an actual business process. When you have created a formal identification for an actual business process you can create formal identifications for its external states and workflow attributes.</Paragraph>
		<Paragraph>Formal identifications must be used in session scripts to reference a business process, external state or workflow attribute.</Paragraph>
		<Paragraph>The main reasons for using formal identifications is that they are maintained at one location outside the session scripts and business processes. At implementation you have the flexibility to define the business processes to which the formal identifications must refer.</Paragraph>
		<List><ListItem><Link href="#A" role="internal">To create a formal identification</Link>
			</ListItem>
		</List>
		<GeneralSection ID="A"><Paragraph>You can create a formal identification for a business process and the external states and workflow attributes of a business process.</Paragraph>
			<Paragraph>The session can only be started if the Workflow enabled field in the <Link href="/baanerp/tg/brg/tgbrg0135s000" role="session">DEM Parameters (tgbrg0135s000)</Link> session is set to modeling.</Paragraph>
			<Paragraph>To be able to define formal identifications for the workflow attributes and external states of a business process, you first need to define a formal identification for the business process itself.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListItem>The name of the formal business process is free. However, to identify one, you are adviced use the package and module code as the first characters of the formal business process name.</ListItem>
					<ListItem>Be aware that the formal identification of a business process is a reference to a business process version. So, if the version of an actual business process changes, the reference in the formal identification must also be modified to this new version. Of course, situations can occur in which you first want to change a whole lot of business processes before they become active.</ListItem>
				</List>
			</Note>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
