<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3AProcess_Templates</id>
		<title>Trends:Process Templates - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3AProcess_Templates"/>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Templates&amp;action=history"/>
		<updated>2026-07-05T08:49:47Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.2</generator>

	<entry>
		<id>https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Templates&amp;diff=5182&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;{{DISPLAYTITLE: Process Templates}} == The Process Templates Trend == Process templates is an overarching term that describes prebuilt business process design, execution and m...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Process_Templates&amp;diff=5182&amp;oldid=prev"/>
				<updated>2017-01-10T12:44:46Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{DISPLAYTITLE: Process Templates}} == The Process Templates Trend == Process templates is an overarching term that describes prebuilt business process design, execution and m...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{DISPLAYTITLE: Process Templates}}&lt;br /&gt;
== The Process Templates Trend ==&lt;br /&gt;
Process templates is an overarching term that describes prebuilt business process design, execution and management artifacts that accelerate time to solution. They are also known by various names, such as &amp;quot;solution frameworks,&amp;quot; &amp;quot;solution templates,&amp;quot; &amp;quot;solution kits,&amp;quot; &amp;quot;starter kits,&amp;quot; &amp;quot;process accelerators&amp;quot; and &amp;quot;process pods&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Process templates should be agnostic and vendor neutral. Typically, process templates are graphical and are based on process flows, rules or service- oriented architecture (SOA). The contents vary dramatically vendor or provider. Some offer simple visual process models that are useful in jump-starting discussions about target processes for improvement. Others provide prebuilt detailed process models, technical reference models, candidate service definitions, technical service libraries, rule sets, user interface templates, simulation scenarios, recommended governance policies, delivery and deployment guides, and process improvement methodologies. &lt;br /&gt;
&lt;br /&gt;
Some vendors sell process templates as products, while others treat them as software assets primarily intended for use in professional service engagements. Process templates are not intended to deliver 100% of a solution. Instead, they are meant to be changed by an implementer. A process template can be extended (that is, the implementer can add capability beyond what was provided by the original assets). It can also be adjusted or configured to accommodate the unique requirements of a process. In many cases, process templates are designed to allow business stakeholders to extend the solution, not just IT personnel. &lt;br /&gt;
&lt;br /&gt;
Process templates use models to manipulate one or more aspects of the process. Some templates are broad (including activities, rules, workflows and UIs), and some are narrow, such as a rule set only. Nevertheless, in the business modelling market, model-driven prebuilt solution content is typically referred to as &amp;quot;process templates.&amp;quot; With process templates, the resulting application is driven by the metadata reflected in the process model. This means that the application's behavior is determined by direct manipulation of the explicit process model, rather than through the setting of parameters or by writing code. Instead of parameters, which restrict application behavior to predetermined options only, a process orchestration engine reads the explicit business process model and directly executes it.&lt;br /&gt;
&lt;br /&gt;
[[Category: Industry Trends]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	</feed>