<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>IBM BAW Tips Q&amp;A - Recent questions and answers in Best Practices</title>
<link>https://bpm.tips/qa/best-practices</link>
<description>Powered by Question2Answer</description>
<item>
<title>Answered: Various ways of implementing logging in a Process Application?</title>
<link>https://bpm.tips/107/various-ways-of-implementing-logging-in-a-process-application?show=3336#a3336</link>
<description>&lt;p&gt;Logging options in a process application, from built-in to custom:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;log.info / log.debug / log.error&lt;/strong&gt; in server-side scripts - goes to SystemOut.log of the member (BAW: also the WLE trace loggers); free, always there, but mixed with the server log. Prefix messages with app acronym and instance id.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Activity / step logging in the engine&lt;/strong&gt;: Process Admin &amp;gt; instance details, the execution tree and the &lt;em&gt;Process Inspector&lt;/em&gt; record every step with timestamps - the audit trail of the flow itself; no code needed.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Instance comments&lt;/strong&gt; (the comments API of the instance, REST or JavaScript) - human-readable notes attached to the instance, visible in the portal; good for business-relevant events (&quot;credit check overridden by X&quot;).&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Tracking groups&lt;/strong&gt; - structured business events into the Performance Data Warehouse (and BAI on CP4BA); the right place for &quot;what happened when&quot; analytics, not for debugging.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Custom log table&lt;/strong&gt; - a toolkit service that inserts (timestamp, app, instance, step, level, message, user) into your own table; queryable, retention under your control; the most common enterprise choice.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Java logging framework&lt;/strong&gt; (log4j / java.util.logging in a managed jar) - files per app with rotation (question 1022); on CP4BA write to stdout instead and let the platform collect.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Central log shipping&lt;/strong&gt; - SystemOut / stdout to ELK / Splunk / OpenShift logging; combine with a JSON log line format from your log service so that dashboards can filter by instance id.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Browser side&lt;/strong&gt; - console.log in coach views for development; an &quot;audit&quot; Service Call for user actions worth keeping.&lt;/li&gt;&lt;/ul&gt;&lt;pre&gt;// toolkit service flow &quot;Log&quot; (level, message) - script writing a structured line to SystemOut / stdout
var line = JSON.stringify({ ts: new Date().toISOString(), app: tw.system.model.processApp.acronym, piid: tw.system.currentProcessInstanceID, user: tw.system.user.name, level: tw.local.level, msg: tw.local.message });
if (tw.local.level == &quot;ERROR&quot;) log.error(line); else log.info(line);&lt;/pre&gt;&lt;p&gt;Guideline: the engine&#039;s own history + tracking groups cover most needs; add one custom log service for technical diagnostics with a level switch in an EPV; never log personal data or secrets; keep logs out of the BPMDB (no custom tables in it).&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/support/knowledgecenter/SS8JB4/com.ibm.wbpm.ref.doc/ae/doc/JSAPI.html&quot;&gt;JavaScript API - log object, comments&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - tracking groups and monitoring&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/107/various-ways-of-implementing-logging-in-a-process-application?show=3336#a3336</guid>
<pubDate>Sun, 06 Sep 2026 13:18:16 +0000</pubDate>
</item>
<item>
<title>Answered: How can we combine all our javascript functions into a single reusable location using Server Files?</title>
<link>https://bpm.tips/115/how-can-we-combine-all-our-javascript-functions-into-a-single-reusable-location-using-server-files?show=3330#a3330</link>
<description>&lt;p&gt;Put the functions in one JavaScript file as a managed web asset, expose them under a single namespace, and include the file from one coach view that every coach carries - then every client-side script and control event can call them (question 3123 shows the same for CSHS scripts). A structure that stays maintainable as the file grows:&lt;/p&gt;&lt;pre&gt;// common.js  (managed web file &quot;common.js&quot; or inside common.zip/js/common.js)
(function (ns) {
  // validation
  ns.isEmail = function (s) { return /^[^@\s]+@[^@\s]+\.[^@\s]+$/.test(s || &quot;&quot;); };
  ns.required = function (control, msg) { var ok = !!control.getData(); control.setValid(ok, ok ? &quot;&quot; : (msg || &quot;Required&quot;)); return ok; };
  // formatting
  ns.money = function (n, cur) { return (cur || &quot;EUR&quot;) + &quot; &quot; + (Math.round((n || 0) * 100) / 100).toFixed(2); };
  ns.date  = function (d) { d = new Date(d); return isNaN(d) ? &quot;&quot; : d.toISOString().slice(0, 10); };
  // UI helpers
  ns.notify = function (alertControl, style, text) { alertControl.setColorStyle(style); alertControl.setText(text); alertControl.setVisible(true); };
  // REST helper (BPM REST API, CSRF aware)
  ns.rest = function (method, path, body, cb) { /* see the answers on REST calls from coach views */ };
  ns.version = &quot;1.3.0&quot;;
})(window.myco = window.myco || {});&lt;/pre&gt;&lt;ol&gt;&lt;li&gt;Coach view &lt;em&gt;Common Library&lt;/em&gt; (no layout) &amp;gt; Behavior &amp;gt; &lt;em&gt;Included Scripts&lt;/em&gt;: common.js. Add this view to a header view that all coaches use, so nobody forgets it.&lt;/li&gt;&lt;li&gt;Use from anywhere: myco.required(${Email}, &quot;E-mail is required&quot;), myco.money(${Total}.getData()).&lt;/li&gt;&lt;li&gt;Version the file name when you change signatures (common-1.3.js), keep the source in Git, minify in the build if it grows.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Server-side functions cannot share a file; there the equivalent is a toolkit service per function (or a Java helper class). Keep browser and server helpers separate - tw.local semantics differ.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - managed web files and included scripts&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/115/how-can-we-combine-all-our-javascript-functions-into-a-single-reusable-location-using-server-files?show=3330#a3330</guid>
<pubDate>Sun, 06 Sep 2026 13:16:57 +0000</pubDate>
</item>
<item>
<title>Answered: Identifying and Resolving BPM Security Issues with AppScan?</title>
<link>https://bpm.tips/118/identifying-and-resolving-bpm-security-issues-with-appscan?show=3329#a3329</link>
<description>&lt;p&gt;AppScan (or any DAST / SAST tool) against a BPM / BAW application finds two kinds of things: platform findings (the same for every installation) and your application&#039;s findings. Handling both:&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Platform findings&lt;/strong&gt; - cookie flags, headers, framework versions:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;HttpOnly / Secure on JSESSIONID and LtpaToken2: set in WebSphere (Session management &amp;gt; cookie settings; Global security &amp;gt; LTPA &amp;gt; SSO cookie options).&lt;/li&gt;&lt;li&gt;Missing headers (X-Frame-Options, Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options): add them on IHS (Header always set …) or the load balancer; BAW 20+ ships sensible defaults, CP4BA&#039;s Zen front door sets most of them. Beware: a strict CSP breaks coaches (inline scripts) - use frame-ancestors and nosniff first, CSP script rules only after testing.&lt;/li&gt;&lt;li&gt;Old libraries flagged (Dojo, jQuery in the UI Toolkit): fixed by BAW fix packs / CP4BA image updates - upgrade rather than patch files; document accepted risks with IBM&#039;s security bulletins.&lt;/li&gt;&lt;li&gt;CSRF: the BPMCSRFToken requirement exists since the 2018 cumulative fixes of 8.6 / BAW; on 8.5.7 install the interim fix that adds the CSRF protection, or front the APIs with a gateway.&lt;/li&gt;&lt;li&gt;Information disclosure (server version in headers, verbose error pages): ServerTokens Prod on IHS, custom error pages in the web container, disable the REST API tester (/bpmrest-ui) in production.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;Application findings&lt;/strong&gt; - the ones you fix in the process app:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;XSS&lt;/strong&gt;: Output Text with &lt;em&gt;allow HTML&lt;/em&gt; showing user input, custom coach views writing innerHTML from data - escape (textContent) or sanitise; never build HTML with string concatenation of user data.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Injection&lt;/strong&gt;: SQL statements built from variables in SQL integrations - always parameters (? with SQLParameter); LDAP filters; shell commands in Java integrations.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Authorization&lt;/strong&gt;: REST calls from coaches to instances / tasks the user should not see - BPM enforces teams, but your services must check the user (tw.system.user) before returning data for an id from the request.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Sensitive data in URLs / logs&lt;/strong&gt;: no clear-text ids of people in GET parameters where avoidable; log statements without personal data.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Process: scan a test environment with a test user per role (the crawler must log in), triage findings into platform / app, fix the app ones in the next snapshot, track platform ones against IBM bulletins, and rescan after fix packs. Keep the AppScan login sequence out of the CSRF trap by recording it with the token flow.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/23.0.x?topic=apis-preventing-cross-site-request-forgery&quot;&gt;BAW - preventing cross-site request forgery&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/mysupport/s/&quot;&gt;IBM Support - security bulletins for BAW&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - securing Business Automation Workflow&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/118/identifying-and-resolving-bpm-security-issues-with-appscan?show=3329#a3329</guid>
<pubDate>Sun, 06 Sep 2026 13:16:44 +0000</pubDate>
</item>
<item>
<title>Answered: Bundling and using your static resources in a zip file?</title>
<link>https://bpm.tips/129/bundling-and-using-your-static-resources-in-a-zip-file?show=3326#a3326</link>
<description>&lt;p&gt;Web assets that belong together (a library with its CSS, fonts and images, or a whole SPA build) are best uploaded as &lt;strong&gt;one zip&lt;/strong&gt; managed file: the coach runtime serves the zip&#039;s entries as if they were a folder, so relative references inside the files keep working.&lt;/p&gt;&lt;ol&gt;&lt;li&gt;Build the folder locally: mylib/js/lib.js, mylib/css/lib.css, mylib/fonts/…, mylib/img/…; zip it &lt;em&gt;without&lt;/em&gt; the top-level folder if you want short paths (zip -r mylib.zip js css fonts img).&lt;/li&gt;&lt;li&gt;Toolkit / app &amp;gt; Files &amp;gt; &lt;em&gt;Web files&lt;/em&gt; &amp;gt; upload mylib.zip.&lt;/li&gt;&lt;li&gt;Reference entries in a coach view&#039;s &lt;em&gt;Included Scripts&lt;/em&gt;: mylib.zip/js/lib.js, mylib.zip/css/lib.css - the picker lets you browse into the zip.&lt;/li&gt;&lt;li&gt;Inside lib.css, url(../fonts/font.woff2) resolves inside the zip; inside JavaScript, compute the base from the script&#039;s own URL when you need it:&lt;/li&gt;&lt;/ol&gt;&lt;pre&gt;// find where the zip is served (works on every release / CP4BA prefix) from a script that is inside the zip
var scripts = document.getElementsByTagName(&quot;script&quot;), base = &quot;&quot;;
for (var i = 0; i &amp;lt; scripts.length; i++) if (/mylib\.zip\/js\/lib\.js/.test(scripts[i].src)) base = scripts[i].src.replace(/js\/lib\.js.*$/, &quot;&quot;);
var img = document.createElement(&quot;img&quot;); img.src = base + &quot;img/logo.png&quot;;&lt;/pre&gt;&lt;p&gt;Advantages: one upload per version, atomic updates, no 60 single files in the library, relative paths intact; the entries are cached by the browser with the snapshot id in the URL, so a new snapshot invalidates them. Limits: the zip is loaded into memory when first requested - keep it under a few MB (no full node_modules), and do not put server files (jars) into web zips - those go to &lt;em&gt;Server files&lt;/em&gt;. To update a single file you still re-upload the whole zip (keep the source folder in Git and script the packaging).&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - managed web files (zip archives) and included scripts&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/129/bundling-and-using-your-static-resources-in-a-zip-file?show=3326#a3326</guid>
<pubDate>Sun, 06 Sep 2026 13:16:06 +0000</pubDate>
</item>
<item>
<title>Answered: What are the reuse principles in IBM BPM, How much reuse becomes too much and a maintenance nightmare?</title>
<link>https://bpm.tips/198/what-are-the-reuse-principles-in-ibm-bpm-how-much-reuse-becomes-too-much-and-a-maintenance-nightmare?show=3316#a3316</link>
<description>&lt;p&gt;Reuse principles that hold in BPM / BAW projects:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Reuse by dependency, not by copy&lt;/strong&gt; - toolkits with snapshots; copying artifacts between apps creates versions nobody maintains.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Reuse stable things&lt;/strong&gt; - domain business objects, integration facades, UI house style, utilities (logging, error handling, configuration). Processes themselves rarely reuse well; sub-processes / linked processes only for genuinely identical steps (approval loop, document request).&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Small toolkits by purpose&lt;/strong&gt;, one owner each, semantic versions, additive changes within a version line.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Interfaces over implementations&lt;/strong&gt; - a reused service has a documented contract (inputs, outputs, errors, side effects) and a test dashboard; callers depend on the contract.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Configuration, not variants&lt;/strong&gt; - one service with EPV / options beats three copies with small differences.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;&lt;strong&gt;When reuse becomes too much&lt;/strong&gt;:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;A &quot;common&quot; toolkit that every app depends on and that changes weekly - each change forces every app to re-test; split it.&lt;/li&gt;&lt;li&gt;Generic services with many mode flags (&quot;action = create|update|delete|validate&quot;) that nobody dares to change - the coupling is now in the parameters.&lt;/li&gt;&lt;li&gt;Reusing a coach view by giving it 40 configuration options - a second, simpler view is cheaper than the option jungle.&lt;/li&gt;&lt;li&gt;Toolkit dependency chains five levels deep - upgrades take days; flatten.&lt;/li&gt;&lt;li&gt;Reuse across teams without an owner - the artifact rots; if nobody owns it, inline it.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The yardstick: reuse pays when the reused artifact changes less often than its consumers and has one owner; when the reused part changes with every project, it is shared code in disguise and should be split or copied deliberately (with a note where it came from).&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - toolkits and dependencies&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/198/what-are-the-reuse-principles-in-ibm-bpm-how-much-reuse-becomes-too-much-and-a-maintenance-nightmare?show=3316#a3316</guid>
<pubDate>Sun, 06 Sep 2026 13:13:55 +0000</pubDate>
</item>
<item>
<title>Answered: How much artifact documentation is optimal, what is the right time to put in documentation design time or release time, since artifacts and design evolves as we develop?</title>
<link>https://bpm.tips/354/much-artifact-documentation-optimal-what-right-documentation-design-release-since-artifacts-design-evolves-develop?show=3312#a3312</link>
<description>&lt;p&gt;Documentation of BPM artifacts is optimal when a reader who did not build the app can operate, change and reuse it without reading every script. Practical rules that work in teams:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Document the &quot;why&quot; in the artifact, the &quot;how&quot; in the model&lt;/strong&gt;: the BPD&#039;s documentation field states the business purpose, owner, SLAs and the events that start / end it; each activity&#039;s documentation says what it decides and which system it touches; scripts get a one-line comment per block. Anything that cannot be seen in the diagram (correlation keys, retry behaviour, assumptions about data) must be written down.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Toolkit artifacts always&lt;/strong&gt;: every service, business object and coach view meant for reuse has its documentation filled (inputs, outputs, side effects, example) - that is what appears in the designer when someone picks it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Snapshot notes&lt;/strong&gt;: the snapshot description carries the change log (&quot;2.3: added credit check, new EPV creditLimit, needs env var crmUrl&quot;); the release manager reads only this.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Naming beats documentation&lt;/strong&gt;: verbs for services (&quot;Get customer&quot;, &quot;Validate order&quot;), nouns for BOs, a prefix per toolkit; a consistent naming standard removes half of the need for text.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Do not document&lt;/strong&gt;: what the diagram already says (&quot;this gateway checks the amount&quot;), generated artifacts, and transient playback services.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;When&lt;/strong&gt;: while building - the documentation fields are part of the definition of done for an artifact; a review checks them like code. Retrofitting documentation on a finished app is the expensive way. The design documents outside the tool (solution architecture, integration contracts, environment configuration) are separate and stay in the wiki / repository with the twx exports; link them from the process app&#039;s documentation field. A useful yardstick: a new developer should be able to explain the process to the business analyst after reading the BPD and its activity documentation - if they need the scripts, documentation is missing.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a target=&quot;_blank&quot; rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/docs/en/baw/24.0.x&quot;&gt;BAW documentation - documenting library items and snapshots&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/354/much-artifact-documentation-optimal-what-right-documentation-design-release-since-artifacts-design-evolves-develop?show=3312#a3312</guid>
<pubDate>Sun, 06 Sep 2026 13:13:04 +0000</pubDate>
</item>
<item>
<title>Answered: Any tool available for Project/code analysis in BPM like Wombat</title>
<link>https://bpm.tips/2754/any-tool-available-for-project-code-analysis-in-bpm-like-wombat?show=2757#a2757</link>
<description>IDA has a checkstyle feature which checks for around 80 code anomalies</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2754/any-tool-available-for-project-code-analysis-in-bpm-like-wombat?show=2757#a2757</guid>
<pubDate>Thu, 05 Dec 2019 22:58:45 +0000</pubDate>
</item>
<item>
<title>Answered: How do you propogate changes to 100Custom.xml to all runtime nodes in a clustered environment?</title>
<link>https://bpm.tips/2707/how-do-you-propogate-changes-to-100custom-xml-to-all-runtime-nodes-in-a-clustered-environment?show=2722#a2722</link>
<description>&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.ibm.com/support/knowledgecenter/en/SS8JB4/com.ibm.wbpm.admin.doc/topics/deployingconfigurationfiles.html&quot;&gt;https://www.ibm.com/support/knowledgecenter/en/SS8JB4/com.ibm.wbpm.admin.doc/topics/deployingconfigurationfiles.html&lt;/a&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2707/how-do-you-propogate-changes-to-100custom-xml-to-all-runtime-nodes-in-a-clustered-environment?show=2722#a2722</guid>
<pubDate>Wed, 20 Nov 2019 18:44:34 +0000</pubDate>
</item>
<item>
<title>Answered: Can someone post a Code Review Checklist for IBM BPM Process Application?</title>
<link>https://bpm.tips/197/can-someone-post-a-code-review-checklist-for-ibm-bpm-process-application?show=2619#a2619</link>
<description>&lt;p&gt;We have built&amp;nbsp;a automated code review tool &quot;Dosvak Code Analyzer&quot; which checks for the following items&lt;/p&gt;&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.dosvak.com/?page_id=1506&quot;&gt;Product Page with Live Demo&lt;/a&gt;&lt;/p&gt;&lt;table&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Non-Parametrized queries&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;Script&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Compexity Score Per PO&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;Application/Model&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Recursive Activity Link BPD&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;10&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Recursive Component Link&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;10&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconverted BPD to Process&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconverted Services&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconverted HHS to CSHS&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Combined too many ajax calls in Load handler&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Table control heavily loaded with Coach Views&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Tab / Stack used with too many tabs&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Deeply nested Coach Views&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;SQL calls in a loop&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Java Connector in a loop&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Web Service invocation in a loop&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Repeated Ajax Services on Coach&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;BPD swimlane assigned to All Users&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;System Tasks delete at completion not checked&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Auto-tracking of BPDs turned on&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Large HHS/CSHS Context Size&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Large BPD Context Size&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;BPD Claim Check Pattern not used&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;BPD Envelope Pattern not used&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Too Large Variables&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWClass&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Human Service Complexity Score - Too complex Human Service/CSHS&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;BPD Complexity Score - Too complex BPDs&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Direct access to Product DB&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;Script&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;System Activity as first step of Multi-Instance Loop&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;8&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Heavily Loaded Coaches&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Large Number of Steps before Coach&lt;/td&gt;&lt;td&gt;1&lt;/td&gt;&lt;td&gt;7&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Decision Services in Loop&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Missing Error Handling JavaConnector&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;All User Exposure BPD&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;6&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Too many steps in a BPD&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Script Length &amp;gt; 2000&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;Script&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;There is no script Content (Empty Script)&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;Script&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;No Usage of Resource Bundles&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;ResourceBundleGroup&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Empty Server Definitions ECM/REST/WEB SERVICE&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;Application/Model&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Service Steps with Unknown in Name&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Dead Branches and steps in BPD&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Mixed Brazos and OOB controls&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconnected End Points in BPDs&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;BPD&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconnected End Points in Human Services&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Unconnected End Points in services&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;TWProcess&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Large Coach Views with too many controls - (Atomic Coach Views)&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;4&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;Prototype Event Handler not enabled for multiple usages in a Coach&lt;/td&gt;&lt;td&gt;2&lt;/td&gt;&lt;td&gt;5&lt;/td&gt;&lt;td&gt;CoachView&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/197/can-someone-post-a-code-review-checklist-for-ibm-bpm-process-application?show=2619#a2619</guid>
<pubDate>Sun, 14 Jul 2019 16:17:37 +0000</pubDate>
</item>
<item>
<title>Answered: What tools are available for automated code review a.k.a static analysis of Snapshot/twx?</title>
<link>https://bpm.tips/2615/what-tools-are-available-for-automated-code-review-a-k-a-static-analysis-of-snapshot-twx?show=2616#a2616</link>
<description>&lt;p&gt;As per our knowledge there are 3 tools available&lt;/p&gt;&lt;p&gt;1. BP-3 Neeches - Software as a service application&lt;/p&gt;&lt;p&gt;2. IDA - IBM Deployment accelerator besides having automated testing capabilities has a CodeStyle feature which checks for about 80 rules, in house stand alone application which pulls snspahots from a process Center.&lt;/p&gt;&lt;p&gt;3. Dosvak Code Analyzer - Our&amp;nbsp;own tool which is just released with 180+ customizable rules along with service and process diagrams to pinpoint the issue. Provided as a Process Application which you can self host on your Process Center or Process Server, unlimited usages.&lt;/p&gt;&lt;p&gt;Live Demo available at&amp;nbsp;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.dosvak.com/?page_id=1506&quot;&gt;Product Page&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;img alt=&quot;&quot; src=&quot;https://bpm.tips/?qa=blob&amp;amp;qa_blobid=3036384015122622002&quot; style=&quot;height:268px; width:600px&quot;&gt;&lt;/p&gt;&lt;p&gt;4. salient Process is building a twx analyzer but is currently more of a structure analysis rather that static analysis agains errors and best practices&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2615/what-tools-are-available-for-automated-code-review-a-k-a-static-analysis-of-snapshot-twx?show=2616#a2616</guid>
<pubDate>Sat, 13 Jul 2019 11:56:05 +0000</pubDate>
</item>
<item>
<title>Answered: Is it right approach to implement a process with two start , in which one of them is start message event and another is plain start?.</title>
<link>https://bpm.tips/2535/is-it-right-approach-to-implement-process-with-two-start-in-which-one-of-them-start-message-event-and-another-plain-start?show=2538#a2538</link>
<description>Yes, It is the right approach if you want to start the BPD or process by UCA also.</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2535/is-it-right-approach-to-implement-process-with-two-start-in-which-one-of-them-start-message-event-and-another-plain-start?show=2538#a2538</guid>
<pubDate>Mon, 20 May 2019 02:06:25 +0000</pubDate>
</item>
<item>
<title>Answered: What are examples of some reusable organization wide toolkits/COE toolkits?</title>
<link>https://bpm.tips/2492/what-are-examples-of-some-reusable-organization-wide-toolkits-coe-toolkits?show=2493#a2493</link>
<description>Enterprise Identity Toolkit&lt;br /&gt;
&lt;br /&gt;
Data Cleanup Toolkit&lt;br /&gt;
&lt;br /&gt;
LDAP Toolkit&lt;br /&gt;
&lt;br /&gt;
Global Cached Static Data Toolkit&lt;br /&gt;
&lt;br /&gt;
Governance and Deployment Toolkit/Process Application&lt;br /&gt;
&lt;br /&gt;
Environment Monitoring Toolkit&lt;br /&gt;
&lt;br /&gt;
Global User Management Toolkit&lt;br /&gt;
&lt;br /&gt;
Logging Toolkit&lt;br /&gt;
&lt;br /&gt;
Global Configuration Toolkit&lt;br /&gt;
&lt;br /&gt;
Content Management Toolkit&lt;br /&gt;
&lt;br /&gt;
Common Utilities Toolkit – pdf, excel, file operations etc.&lt;br /&gt;
&lt;br /&gt;
Enterprise Domain Business Objects Toolkit&lt;br /&gt;
&lt;br /&gt;
Exception Handling Toolkit&lt;br /&gt;
&lt;br /&gt;
Log Analysis Toolkit&lt;br /&gt;
&lt;br /&gt;
Code Review and Analysis Toolkit&lt;br /&gt;
&lt;br /&gt;
Regression Testing Toolkits</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2492/what-are-examples-of-some-reusable-organization-wide-toolkits-coe-toolkits?show=2493#a2493</guid>
<pubDate>Fri, 14 Dec 2018 14:53:15 +0000</pubDate>
</item>
<item>
<title>Answered: What are the essential Documents which need to be created to Establish a BPM Center of Excellence ?</title>
<link>https://bpm.tips/2490/what-are-the-essential-documents-which-need-to-be-created-to-establish-a-bpm-center-of-excellence?show=2491#a2491</link>
<description>&lt;p&gt;Following are some of the base set of documents which need to be created&lt;/p&gt;&lt;p&gt;1. &lt;strong&gt;Application Environment Configurations &lt;/strong&gt;- This should be created and maintained at a central location for Each Application.&lt;/p&gt;&lt;p&gt;2. &lt;strong&gt;COE Application Inventory&lt;/strong&gt; - This is one per COE carrying a listing with high level overview and elementary details about each on-boarded application.&lt;/p&gt;&lt;p&gt;3. &lt;strong&gt;Application Overview Template&lt;/strong&gt; - A Template providing guidelines to create an overview per application.&lt;/p&gt;&lt;p&gt;4. &lt;strong&gt;Architectural Guidelines &lt;/strong&gt;- Architectural guidelines to be followed while designing and developing Process Applications.&lt;/p&gt;&lt;p&gt;5. &lt;strong&gt;Artifact Naming Conventions&lt;/strong&gt; - It is recommended to have a globally applicable naming conventions for all your artifacts spread across different Process Applications.&lt;/p&gt;&lt;p&gt;6. &lt;strong&gt;Code Review Checklist -&amp;nbsp;&lt;/strong&gt;A centrally maintained code review checklist to be adhered to by the Process Application Teams.&lt;/p&gt;&lt;p&gt;7. &lt;strong&gt;COE Standardization Toolkits&lt;/strong&gt; - standardization reusable toolkits like environment variable toolkit, content management toolkits, custom controls, Business Objects toolkits, Look and Feel Template Toolkits should be developed to promote reuse and central management of configurations.&lt;/p&gt;&lt;p&gt;8. &lt;strong&gt;Deployment Procedures -&amp;nbsp;&lt;/strong&gt;&amp;nbsp;Deployment Procedures should be goverened at COE level and directions provided via this document.&lt;/p&gt;&lt;p&gt;9. &lt;strong&gt;Development Best Practices&lt;/strong&gt; - Recommended Best practices should be documented as development and design guidelines for new applications and developers.&lt;/p&gt;&lt;p&gt;10. &lt;strong&gt;In-Flight Migration Considerations&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;11. &lt;strong&gt;Integration Best Practices and Directives&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;12. &lt;strong&gt;Non-Functional Requirements Template&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;13. &lt;strong&gt;PDW Reporting Guidelines&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;14. &lt;strong&gt;Performance Considerations and Guidelines&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;15. &lt;strong&gt;Recommended Design Patterns&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;16. &lt;strong&gt;Project Charter Template&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;17. &lt;strong&gt;Project LifeCycle and Development Methodology Guidelines&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;18. &lt;strong&gt;Security Considerations and Best Practices&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;19. &lt;strong&gt;Project Sizing and Estimation Worksheets&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;20. &lt;strong&gt;Application validation and Smoke Testing Procedures Manual - Per application&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;21. &lt;strong&gt;Unit Testing Best Practices&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;22. &lt;strong&gt;User Interfaces UI and UX Guidelines&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;23. &lt;strong&gt;User/Team/PG Management Guidelines&lt;/strong&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/2490/what-are-the-essential-documents-which-need-to-be-created-to-establish-a-bpm-center-of-excellence?show=2491#a2491</guid>
<pubDate>Fri, 14 Dec 2018 14:29:19 +0000</pubDate>
</item>
<item>
<title>Answered: What are the Use Cases you are familiar with for IBM BPM Process Applications, some I know of are as follows?</title>
<link>https://bpm.tips/1429/what-are-the-use-cases-you-are-familiar-with-for-ibm-bpm-process-applications-some-i-know-of-are-as-follows?show=2417#a2417</link>
<description>Loan Origination&lt;br /&gt;
Financial Fraud Detection&lt;br /&gt;
Banking KYC Process (Know Your Customer)&lt;br /&gt;
Financial Complance&lt;br /&gt;
Supply Chain&lt;br /&gt;
Enterprise Content Management &amp;amp; Organization&lt;br /&gt;
Static Data Maintenance&lt;br /&gt;
Credit Evaluation&lt;br /&gt;
Customer Due Diligence&lt;br /&gt;
Patient Wellness and Care Management&lt;br /&gt;
Asset Management&lt;br /&gt;
Change Management and Excursions&lt;br /&gt;
Patient Survey Call Center&lt;br /&gt;
Cash Flow Management&lt;br /&gt;
Financial Workflows</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/1429/what-are-the-use-cases-you-are-familiar-with-for-ibm-bpm-process-applications-some-i-know-of-are-as-follows?show=2417#a2417</guid>
<pubDate>Sat, 20 Oct 2018 16:43:11 +0000</pubDate>
</item>
<item>
<title>Answered: How can we determine if Product Database is being accessed from a Process Application?</title>
<link>https://bpm.tips/1411/how-can-we-determine-if-product-database-is-being-accessed-from-a-process-application?show=2413#a2413</link>
<description>&lt;p&gt;One quick way will be to search for LSW_ in a twx, how to seaerch a twx is described at the following thread&lt;/p&gt;&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://bpm.tips/79/how-can-we-search-for-a-certain-string-in-an-entire-process-app-from-process-server-database?show=79#q79&quot;&gt;https://bpm.tips/79/how-can-we-search-for-a-certain-string-in-an-entire-process-app-from-process-server-database?show=79#q79&lt;/a&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/1411/how-can-we-determine-if-product-database-is-being-accessed-from-a-process-application?show=2413#a2413</guid>
<pubDate>Sat, 20 Oct 2018 15:44:45 +0000</pubDate>
</item>
<item>
<title>Answered: What are the best automated testing tools for IBM BPM?</title>
<link>https://bpm.tips/1083/what-are-the-best-automated-testing-tools-for-ibm-bpm?show=1085#a1085</link>
<description>&lt;p&gt;Two prominent products which come to mind are&lt;/p&gt;&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.royalcyber.com/resources/webcasts/ibm-business-process-manager-test-automation-with-behavior-driven-framework&quot;&gt;https://www.royalcyber.com/resources/webcasts/ibm-business-process-manager-test-automation-with-behavior-driven-framework&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a rel=&quot;nofollow&quot; href=&quot;https://www.capbpm.com/capq/&quot;&gt;https://www.capbpm.com/capq/&lt;/a&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/1083/what-are-the-best-automated-testing-tools-for-ibm-bpm?show=1085#a1085</guid>
<pubDate>Fri, 13 Oct 2017 22:30:59 +0000</pubDate>
</item>
<item>
<title>Answered: What is best practice for stopping and starting a Production Process Server/Cluster?</title>
<link>https://bpm.tips/125/what-is-best-practice-for-stopping-and-starting-a-production-process-server-cluster?show=442#a442</link>
<description>Use ripple start.&lt;br /&gt;
&lt;br /&gt;
In WAS Admin console there is a button on &amp;quot;servers&amp;quot; page.&lt;br /&gt;
&lt;br /&gt;
using script (Jacl) &amp;gt;&amp;gt; $AdminControl invoke $cluster rippleStart</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/125/what-is-best-practice-for-stopping-and-starting-a-production-process-server-cluster?show=442#a442</guid>
<pubDate>Thu, 30 Jun 2016 07:14:10 +0000</pubDate>
</item>
<item>
<title>Answered: What are the unit testing Best Practices for a IBM BPM Process application?</title>
<link>https://bpm.tips/131/what-are-the-unit-testing-best-practices-for-a-ibm-bpm-process-application?show=360#a360</link>
<description>Unit Testing/debugging is generally done by launching a service from Process Designer or from Process Inspector, If you have complex services or Processes Ideally you should have two monitor where in on one you see the task/service executing in browser and on the other the Process Inspector shows where the token is. This is fine when developing. But for maintenance regression and modification purposes the Best practice is to have a Unit Test Wrapper Service with data constructors, coupled with select drop downs for providing various combinations of input data to the underlying service which is being tested. You may also want to put in a display coach at the end of invocation if the service outputs data which needs to be validated.&lt;br /&gt;
&lt;br /&gt;
We build Unit Test Wrappers or also called Test Harnesses for&lt;br /&gt;
&lt;br /&gt;
1. Human Tasks (to make then runnable outside a process, though they actually run in a process)&lt;br /&gt;
2. Standalone Services (Which Run independently of a Process)&lt;br /&gt;
3. Processes which take input data through a message start&lt;br /&gt;
4. Reusable Integrations (place them in functional area toolkits with included Test Harnesses)</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/131/what-are-the-unit-testing-best-practices-for-a-ibm-bpm-process-application?show=360#a360</guid>
<pubDate>Wed, 08 Jun 2016 22:01:05 +0000</pubDate>
</item>
<item>
<title>Answered: What are the recommended naming Conventions for Services, BPDS, variables, etc.</title>
<link>https://bpm.tips/195/what-are-the-recommended-naming-conventions-for-services-bpds-variables-etc?show=329#a329</link>
<description>&lt;p&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;BPD naming convention&lt;/strong&gt;&lt;/span&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:ubuntu,helvetica,arial,freesans,sans-serif; font-size:16px&quot;&gt;&amp;nbsp;- The primary or top level BPD should be clearly marked with some Pre-fix or Post-fix identifier e.g. Primary Process or Top Level, All BPDs are generally named with the format&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:arial,sans-serif; font-size:10pt&quot;&gt;{Verb}{Noun} . e.g.,&amp;nbsp;Review Request, Approve Request, Submit Ad-hoc Request, Process&amp;nbsp;Ad-hoc Request etc.&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Service naming convention&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;- {type} {verb}{noun} - Type should specify system or the type of the service. For UI services every service should start with UI. &amp;nbsp;Wording should be with capital letters and space between each word. For preposition (on, at, in. etc.) words use a small letter instead of capital letter. Examples:&amp;nbsp;SYSTEMA Get Supplier Details,&amp;nbsp;SYSTEMB Get Supplier Contact Details,&amp;nbsp;SYSTEMC Submit Extension Request,&amp;nbsp;SAP Create Purchase Order,&amp;nbsp;BIZ Rule Map Purchasing Team to Time Zone, UI Submit Supplier Request etc.&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Variable Types&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;-&amp;nbsp;&lt;/span&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:ubuntu,helvetica,arial,freesans,sans-serif; font-size:16px&quot;&gt;{prefix}{noun}. Prefix could be the Business Entity name or sytem name. Every noun will generically describe the several fields grouped in the Variable Type. It can consist of one word or more. Every word should start with capital letter and there is no spaces or underscore between words. Examples: ProjectRequest, ShoppingCart, PurchaseOrder, etc.&lt;/span&gt;&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Variables&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:ubuntu,helvetica,arial,freesans,sans-serif; font-size:16px&quot;&gt;Camel case - Javascript industry standard – can consist of&amp;nbsp;one or more&amp;nbsp;word . the&amp;nbsp;1st&amp;nbsp;letter small case letter. Every words first letter is a capital letter (except of the 1&lt;/span&gt;&lt;sup&gt;st&lt;/sup&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:ubuntu,helvetica,arial,freesans,sans-serif; font-size:16px&quot;&gt;&amp;nbsp;word). Examples: attestationRequest, businessContext, processContext etc.&lt;/span&gt;&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Snapshot naming convention&amp;nbsp;&lt;/strong&gt;&lt;/span&gt;&lt;strong&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&amp;nbsp;{&lt;/span&gt;&lt;/strong&gt;&lt;span style=&quot;color:rgb(52, 73, 94); font-family:ubuntu,helvetica,arial,freesans,sans-serif; font-size:16px&quot;&gt;Project Name} {Release/Environment name} {Date}​ Future snapshots created on the same date can have a V1, V2 suffix to this format.&lt;/span&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/195/what-are-the-recommended-naming-conventions-for-services-bpds-variables-etc?show=329#a329</guid>
<pubDate>Sun, 05 Jun 2016 10:15:14 +0000</pubDate>
</item>
<item>
<title>Answered: Should BPD Process Application data be treated/used as Record of Origin or Source of Truth ?</title>
<link>https://bpm.tips/289/should-bpd-process-application-data-be-treated-used-as-record-of-origin-or-source-of-truth?show=302#a302</link>
<description>I have come across two school of thoughts on this issue&lt;br /&gt;
&lt;br /&gt;
1. Why have an overhead of updating the Record of Origin or Source of Truth when the BPD is the actual Process Container and holds the latest and greatest version of the data, also there is an overhead involved since after every Data Change Activity e.g. Human Tasks we need to update the application database, also we can use REST APIS to work with the data when we use BPM Processes as the source of truth. Also if the system source of truth is only updated via BPM and there is no need to update it from external applications/systems this approach makes sense.&lt;br /&gt;
&lt;br /&gt;
2. Transaction management is not inherent to the BPM processes and the the BPM processes are not designed for efficient and safe reading and writing of the data simultaneously when processes are operational, also concurrent read and writes have to be kept in mind when we are using BPM as a source of truth. Actually by design IBM BPM is not meant to be used as a source of truth.</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/289/should-bpd-process-application-data-be-treated-used-as-record-of-origin-or-source-of-truth?show=302#a302</guid>
<pubDate>Sat, 28 May 2016 13:40:56 +0000</pubDate>
</item>
<item>
<title>Answered: What is a data constructor Service, why is it needed ?</title>
<link>https://bpm.tips/293/what-is-a-data-constructor-service-why-is-it-needed?show=294#a294</link>
<description>Data Constructor Services are meant to be used as place holders for actual integration services supplying the data eventually, they initially populate hard coded data to the Business Objects for playback and demo purposes and quick prototyping, without any changes to upper level services the actual data integrations can happen at later stages.&lt;br /&gt;
&lt;br /&gt;
Also it is not a recommended practice to have default values for your business objects, thus for unit testing you can use the plugged in data constructor service to provide the test data also.</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/293/what-is-a-data-constructor-service-why-is-it-needed?show=294#a294</guid>
<pubDate>Sun, 22 May 2016 19:18:21 +0000</pubDate>
</item>
<item>
<title>Answered: What are the IBM BPM Development Best Practices?</title>
<link>https://bpm.tips/132/what-are-the-ibm-bpm-development-best-practices?show=290#a290</link>
<description>&lt;p&gt;&lt;u&gt;&lt;strong&gt;1. Usability Standards&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;If there is a large amount of data, it is recommended to use a wizard style user interface wherein user can navigate back and forth between steps maintaining the previous entries they have made&lt;br&gt;User interface should be capable of handling large amount of data without performance degradation.&lt;br&gt;As per business needs audit trail of user actions may or may not be needed&lt;br&gt;Accessibility needs need to be specified if business need is there.&lt;br&gt;All screens should provide consistency in common screens and features e.g. common header/footer, common way of searching etc.&lt;br&gt;Feedback: System should provide appropriate feedback to users e.g. progress icons, on page error messages, dialog boxes with status&lt;br&gt;Bread Crumb/Process Progress Bar, for large processes with a lot of steps and states and statuses it is desirable to provide a progress bar to depict to the users where they are in the process flow.&lt;br&gt;seamless integration with external systems&lt;br&gt;Single Sign on&lt;br&gt;Multiple concurrent sessions may or may not be needed for same tasks screens and appropriate data integrity measures should be implemented, determine as per usage if optimistic locking or pessimistic locking is needed.&lt;br&gt;Security concerns authorization&amp;nbsp;&amp;nbsp;of data at section or element level may need to be addressed with appropriate control/section &amp;nbsp;based authorizations.&lt;br&gt;Required fields should be clearly indicated with different color or with red asterisk.&lt;br&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;u&gt;&lt;strong&gt;2. Naming Standards&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;u&gt;&lt;strong&gt;BPD naming convention&lt;/strong&gt;&lt;/u&gt; - The primary or top level BPD should be clearly marked with some Pre-fix or Post-fix identifier e.g. Primary Process or Top Level, All BPDs are generally named with the format&amp;nbsp;&lt;span style=&quot;font-family:arial,sans-serif; font-size:10.0pt&quot;&gt;{Verb}{Noun} . e.g.,&amp;nbsp;Review Request, Approve Request, Submit Ad-hoc Request, Process&amp;nbsp;Ad-hoc Request etc.&lt;br&gt;&lt;u&gt;&lt;strong&gt;Service naming convention &lt;/strong&gt;&lt;/u&gt;- {type} {verb}{noun} - Type should specify system or the type of the service. For UI services every service should start with UI. &amp;nbsp;Wording should be with capital letters and space between each word. For preposition (on, at, in. etc.) words use a small letter instead of capital letter. Examples:&amp;nbsp;SYSTEMA Get Supplier Details,&amp;nbsp;SYSTEMB Get Supplier Contact Details,&amp;nbsp;SYSTEMC Submit Extension Request,&amp;nbsp;SAP Create Purchase Order,&amp;nbsp;BIZ Rule Map Purchasing Team to Time Zone, UI Submit Supplier Request etc.&lt;br&gt;&lt;u&gt;&lt;strong&gt;Variable Types &lt;/strong&gt;&lt;/u&gt;- &lt;/span&gt;{prefix}{noun}. Prefix could be the Business Entity name or sytem name. Every noun will generically describe the several fields grouped in the Variable Type. It can consist of one word or more. Every word should start with capital letter and there is no spaces or underscore between words. Examples: ProjectRequest, ShoppingCart, PurchaseOrder, etc.&lt;br&gt;&lt;u&gt;&lt;strong&gt;Variables &lt;/strong&gt;&lt;/u&gt;Camel case - Javascript industry standard – can consist of&amp;nbsp;one or more&amp;nbsp;word . the&amp;nbsp;1st&amp;nbsp;letter small case letter. Every words first letter is a capital letter (except of the 1&lt;sup&gt;st&lt;/sup&gt; word). Examples: attestationRequest, businessContext, processContext etc.&lt;br&gt;&lt;u&gt;&lt;strong&gt;Snapshot naming convention&amp;nbsp;&lt;/strong&gt;&lt;/u&gt;&lt;strong&gt;&lt;u&gt;&amp;nbsp;{&lt;/u&gt;&lt;/strong&gt;Project Name} {Release/Environment name} {Date}​ Future snapshots created on the same date can have a V1, V2 suffix to this format.&lt;/p&gt;&lt;p&gt;&lt;u&gt;&lt;strong&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:10.0pt&quot;&gt;Code Review Checklist&lt;/span&gt;&lt;/strong&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;font-family:arial,sans-serif&quot;&gt;&lt;span style=&quot;font-size:13.3333px&quot;&gt;1. Is there sufficient documentation of BPD and Service Artifacts is there color coding by type of tasks&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;span style=&quot;font-family:arial,sans-serif&quot;&gt;&lt;span style=&quot;font-size:13.3333px&quot;&gt;2. Is&amp;nbsp;Javascript indented and commented properly&lt;br&gt;3. Is reusable javascript function library created at a central server js file&lt;br&gt;4. Is appropriate usage of caching there&lt;br&gt;5. Is a Unit Test harness built for each task and integration service&lt;br&gt;6. Is sufficient Error Handling in place both at service and BPD level&lt;br&gt;7. What logging mechanism has been used and is sufficient logging there with appropriate logging levels set i.e. info, debug, error, alert&lt;br&gt;8. Is there direct access to Process DB (Product DB), it should be only when absolutely necessary since upgrades and migrations may not go through with Product DB changes&lt;br&gt;9. Is Performance DB being leveraged, has sizing of PDW database needs been done&amp;nbsp;&lt;br&gt;10. Is NOLOCK being used for SQL calls&lt;br&gt;11. Is&amp;nbsp;string concatenation used or StringBuffer&lt;br&gt;12. what is unit tested load time in Development environment per task and integration&lt;br&gt;13. Is parametrized query for sql statements being used&lt;br&gt;14. Is every message on UI and BPD and task attributes connected to a central resource bundle so that they can be changed centrally&lt;br&gt;15. Is there hard coding of Environment specific variables e.g. hostname, port number, webservice endpoint etc. or they are in the environment configuration of the application&lt;br&gt;16. Is there a maintenance shutdown for the Process Application feature implemented&lt;br&gt;18. Are there validation errors in the Process Application&lt;br&gt;19. Is all the static data appropriately cached, and key based caching used for partially cacheable data&lt;br&gt;20. Are there default values set/accidentally left out for service input and output variables&lt;br&gt;21. Are all the static resources for the Process App e.g. css, javascript libraries etc minified and bundled in zip files. images should also be optimized for web delivery&lt;br&gt;22. Are Artifacts&amp;nbsp;appropriately tagged with Company identifier and type of service&lt;br&gt;23. Are all the naming conventions adhered to&lt;br&gt;24. Are decision services being used for business decisions and routing where appropriate&lt;br&gt;25. If copies of existing controls are made they should be placed in a separate toolkit not mixing up with the Process Application code&lt;br&gt;26. Is the business data&amp;nbsp;and process data appropriately bundled in context variables at BPD level so that minimal modifications to BPD is needed if additional data elements need to be added.&lt;/span&gt;&lt;/span&gt;&lt;br&gt;27. Is autotracking turned off in BPDs&lt;br&gt;28. Is save execution context checked on&lt;br&gt;29. Is there service exposure appropriately defined e.g. Admin Services vs Portal Services vs Dashboards&lt;br&gt;30. Is the exposure of services properly governed by teams and no accidental &quot;All Users&quot; exposures are there.&lt;br&gt;31. Is only minimal necessary Business Data exposed.&lt;br&gt;32. Are reusable artifacts e.g. Domain Business Objects, Generic Utility Dashboards etc. properly classified in toolkits.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/132/what-are-the-ibm-bpm-development-best-practices?show=290#a290</guid>
<pubDate>Sun, 22 May 2016 12:00:52 +0000</pubDate>
</item>
<item>
<title>Answered: What are the common Pre/Post Fixes for Services from Lombardi Era, are they still used/applicable?</title>
<link>https://bpm.tips/181/what-are-the-common-pre-post-fixes-for-services-from-lombardi-era-are-they-still-used-applicable?show=182#a182</link>
<description>&lt;p&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;TS&lt;/strong&gt;&lt;/span&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Task Service A service that directly implements an activity. Such a serviceis responsible for coordinating a whole task for a user/system.&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;CS&lt;/strong&gt;&lt;/span&gt; Coach Service A service that implements a single coach. It is generally recommended that a service not have more than a single coach in it.&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Init&lt;/strong&gt;&lt;/span&gt;&amp;nbsp; A service that provides specific initialization functionality for the parent service for which its named&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;Action&lt;/strong&gt;&lt;/span&gt; A service that provides specific post-action functionality for the parent service for which its named&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;ES&lt;/strong&gt;&lt;/span&gt; Event Service A service that is used specifically to invoke an Event Driven UCA&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;EI&lt;/strong&gt;&lt;/span&gt; Event Implementer A service that directly implements an Event Driven UCA&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;BS&lt;/strong&gt;&lt;/span&gt; Batch Service A service that directly implements a Batch/Chron driven UCA&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;US&lt;/strong&gt;&lt;/span&gt; Utility Service A service that implements some piece of utility functionality (such as text parsing for valid email format, etc)&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;WS&lt;/strong&gt;&lt;/span&gt; WebService Service A service that directly implements a Teamworks hosted WebService&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;IS&lt;/strong&gt;&lt;/span&gt; Integration Service A service whose specific purpose it is to wrap a Teamworks Integration connector&lt;br&gt;&lt;span style=&quot;text-decoration: underline;&quot;&gt;&lt;strong&gt;DAS&lt;/strong&gt;&lt;/span&gt; Data AccessService A service whose specific purpose it is to get some data from inside (EPV properties) or outside (DB, LDAP) TeamWorks&lt;/p&gt;&lt;p&gt;These were the Lombardi recommended acronyms, as&amp;nbsp;it is evident from the descriptions some of them are no longer applicable and also there was no categorization or tagging back then and the acronyms made more sense, but I have seen they are still in use in certain projects.&lt;/p&gt;</description>
<category>Best Practices</category>
<guid isPermaLink="true">https://bpm.tips/181/what-are-the-common-pre-post-fixes-for-services-from-lombardi-era-are-they-still-used-applicable?show=182#a182</guid>
<pubDate>Wed, 18 May 2016 00:11:39 +0000</pubDate>
</item>
</channel>
</rss>