Histórico da Página

	
<div id="main-content" class="wiki-content group">
	<h1 id="ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Índice">Contents</h1>
	<p>
		<style type='text/css'>/*<![CDATA[*/
div.rbtoc1412696050514 {
	padding: 0px;
}
div.rbtoc1412696050514 ul {
	list-style: none;
	margin-left: 0px;
}
div.rbtoc1412696050514 li {
	margin-left: 0px;
	padding-left: 0px;
}
/*]]>*/
</style>
	<div class='toc-macro rbtoc1412696050514'>
		<ul class='toc-indentation'>
			<li><span class='TOCOutline'>1</span> <a
				href='#ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Introdução'>Introduction</a></li>
			<li><span class='TOCOutline'>2</span> <a
				href='#ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Scriptcondicional'>Conditional
					Script</a></li>
			<li><span class='TOCOutline'>3</span> <a
				href='#ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Sinal'>Signal</a></li>
		</ul>
	</div>
	</p>
	<h1
		id="ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Introdução">Introduction</h1>
	<p>
		One of the new features of Fluig is the possibility of using an entire
		set of new components from the BPMN 2.0 notation, enabling not only
		the automation of a process but also enabling its documentation for
		the organization. These new components enable the extension of
		features already created with the old components and can be accessed
		using the BPMN Extended button located on the toolbar of your IDE.
		This button allows toggling between the <strong>Main</strong>&#160;and
		<strong>Extended</strong> modes. When this button is pressed, it will
		have an immediate effect upon the palette of components of process
		modeling.
	</p>
	<p>
		<img class="confluence-embedded-image"
			src="http://tdn.totvs.com/download/attachments/126714181/image2014-2-25%2017%3A24%3A24.png?version=1&modificationDate=1393359846000&api=v2"
			data-image-src="http://tdn.totvs.com/download/attachments/126714181/image2014-2-25%2017%3A24%3A24.png?version=1&modificationDate=1393359846000&api=v2">
	</p>
	<p>
		When accessing the <strong>BPMN Extended&#160;</strong>mode, you will
		have an increase of 33 new elements that may be used in any Fluig
		process that you may have in your organization today, extending its
		features.
	</p>
	<h1
		id="ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Scriptcondicional">Conditional
		Script</h1>
	<p>One of the new concepts found in BPMN 2.0 is the addition of
		conditional scripts. Conditional scripts are developed using
		javascript language, and allow Fluig to query external services
		allowing the creation of more elaborate processes. Conditional scripts
		are usually linked to schedulers that determine the period or
		frequency in which these scripts are executed. When the script is able
		to return a logical value equal to true means that the script was
		executed successfully, handling workflow requests according to
		modeling element used.&#160;</p>
	<h1 id="ConfiguraçãodeProcessoscomComponentesAvançados(BPMN2.0)-Sinal">Signal</h1>
	<p>Signals is a new type of communication between processes created
		for fluig. Using signals, a process may handle or start one or more
		workflow requests according to the signal configured. The best way to
		describe the operation of signals is with an example. Below we have
		the process of an automobile sale in which the client has just
		confirmed the purchase. The activity after the purchase activity is an
		intermediate event of sending a signal that has a configured signal,
		named "VendaEfetivada".</p>
	<p>
		<img class="confluence-embedded-image image-center"
			src="http://tdn.totvs.com/download/attachments/126714181/processovenda.png?version=1&modificationDate=1393456609000&api=v2"
			data-image-src="http://tdn.totvs.com/download/attachments/126714181/processovenda.png?version=1&modificationDate=1393456609000&api=v2">
	</p>
	<p>The intermediate event sends the signal and immediately proceed
		to the next activity, allowing the customer to have the automobile in
		his/her possession immediately. &#160;The company that sold the car
		has an insurance department that has a process integrated by a signal.
		It awaits the purchase confirmation from the customer to immediately
		begin assembling the insurance policy and attempts to contact the
		customer with an offer for auto insurance.</p>
	<p>
		<img class="confluence-embedded-image image-center"
			src="http://tdn.totvs.com/download/attachments/126714181/processoseguro.png?version=2&modificationDate=1393457173000&api=v2"
			data-image-src="http://tdn.totvs.com/download/attachments/126714181/processoseguro.png?version=2&modificationDate=1393457173000&api=v2">
	</p>
	<p>The insurance department process has an initial signal-receiving
		event. Every time the store confirms the sale of an automobile, a new
		workflow request is automatically opened in the insurance process that
		shortly thereafter seeks to contact the customer with an offer for
		insurance.&#160;</p>
	<p>Meanwhile, the automobile factory that has finished cars in
		stock is also monitoring the same signal sent by the store, and begins
		its process to replace the automobiles in the store.</p>
	<p>
		<img class="confluence-embedded-image image-center"
			src="http://tdn.totvs.com/download/attachments/126714181/processofabrica.png?version=2&modificationDate=1393457173000&api=v2"
			data-image-src="http://tdn.totvs.com/download/attachments/126714181/processofabrica.png?version=2&modificationDate=1393457173000&api=v2">
	</p>
	<p>Simply by configuring the signals that the events operate, a new
		type of integration can be created between different processes in
		different departments, without any additional programming or
		customization.</p>
	<p>&#160;</p>
	<div class="aui-message warning shadowed information-macro">
		<p class="title">Note</p>
		<span class="aui-icon icon-warning">Icon</span>
		<div class="message-content">
			<p>For a complete understanding of this guide, the user should
				have advanced knowledge of the BPMN Main mode. Otherwise, please
				seek training sessions from TOTVS Academy.</p>
		</div>
	</div>
</div>