Successfully reported this slideshow.

Wielding Workflow


Published on

Published in: Economy & Finance, Technology
  • Be the first to comment

  • Be the first to like this

Wielding Workflow

  1. 1. Wielding Workflow Varadarajan Rajaram, Track: Advanced AppExchange Developers
  2. 2. Safe Harbor Statement <ul><li>“ Safe harbor” statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements the achievement of which involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions proves incorrect, our results could differ materially from the results expressed or implied by the forward-looking statements we make.  All statements other than statements of historical fact could be deemed forward-looking, including any projections of subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. </li></ul><ul><li>The risks and uncertainties referred to above include - but are not limited to - risks associated with the integration of Sendia Corporation’s technology, operations, infrastructure and personnel with ours; unexpected costs or delays incurred in integrating Sendia with, which could adversely affect our operating results and rate of growth; any unknown errors or limitations in the Sendia technology; any third party intellectual property claims arising from the Sendia technology; customer and partner acceptance and deployment of the AppExchange and AppExchange Mobile platforms; interruptions or delays in our service or our Web hosting; our new business model; breach of our security measures; possible fluctuations in our operating results and rate of growth; the emerging market in which we operate; our relatively limited operating history; our ability to hire, retain and motivate our employees and manage our growth; competition; our ability to continue to release and gain customer acceptance of new and improved versions of our CRM service; unanticipated changes in our effective tax rate; fluctuations in the number of shares outstanding; the price of such shares; foreign currency exchange rates and interest rates. </li></ul><ul><li>Further information on these and other factors that could affect our financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings we make with the Securities and Exchange Commission from time to time, including our Form 10-K for the fiscal year ended January 31, 2006. These documents are available on the SEC Filings section of the Investor Information section of our website at . </li></ul><ul><li>Any unreleased services or features referenced in this or other press releases or public statements are not currently available and may not be delivered on time or at all.  Customers who purchase our services should make purchase decisions based upon features that are currently available., inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law. </li></ul>
  3. 3. Agenda <ul><li>Introduction </li></ul><ul><li>Winter ‘07 Workflow – What’s new? </li></ul><ul><li>Focus on approvals </li></ul><ul><li>Q&A – Approvals API </li></ul>
  4. 4. Definition <ul><li>Workflow enables the automation of a business process, in while or part within your organization – from sales, to service, to HR, to finance. It enforces a process within your organization which is consistently followed and improves efficiency and productivity. </li></ul>
  5. 5. Current Workflow Capabilities (Pre Winter ’07) <ul><li>Automated notification </li></ul><ul><ul><li>Review current discount policies on Opportunities </li></ul></ul><ul><ul><li>Follow up on Cases for Platinum Customers </li></ul></ul><ul><li>Limited action types </li></ul><ul><ul><li>Email Alerts </li></ul></ul><ul><ul><li>Create Tasks </li></ul></ul>
  6. 6. Winter ’07 Workflow Capabilities <ul><li>Automate your business processes </li></ul><ul><ul><li>Field Updates, Outbound Messages, Approvals </li></ul></ul><ul><li>Enforce business processes </li></ul><ul><ul><li>Lock down Opportunities when it is closed </li></ul></ul><ul><li>Improve customer satisfaction </li></ul><ul><ul><li>Initiate a customer survey as soon as a Platinum customer case is closed </li></ul></ul><ul><li>Improved data quality </li></ul><ul><ul><li>Store only the last 4 digits of the SSN </li></ul></ul>
  7. 7. Winter ’07 Workflow Capabilities <ul><li>Approval process automation </li></ul><ul><ul><li>Simple and complex multi-step processes </li></ul></ul><ul><ul><li>Supported in the API </li></ul></ul><ul><li>Eliminate laborious manual processes </li></ul><ul><ul><li>Automate and eliminate your paper-based PTO requests </li></ul></ul><ul><li>Control business processes </li></ul><ul><ul><li>Discount policy controls – Enforce approvals on large discounts </li></ul></ul><ul><ul><li>Campaign spending controls – Force approvals on costly campaigns </li></ul></ul>
  8. 8. Winter ’07 Workflow
  9. 9. Field Update Action <ul><li>Automatically change the value in a field as a result of a workflow trigger, including owner and record type! </li></ul>
  10. 10. Outbound Message Action <ul><li>Send a customizable XML message to any desired Web-available listener. No more polling for changes! </li></ul><ul><li>Can be used to automate updates to dependent records! </li></ul><ul><li>Gain automated asynchronous integration with external systems </li></ul>
  11. 11. Other Workflow Enhancements <ul><li>Workflow rule limit increased from 50 to 300 per object </li></ul><ul><li>More standard objects supported </li></ul><ul><ul><li>Opportunity Product </li></ul></ul><ul><ul><li>Order Product </li></ul></ul><ul><li>Advanced “or” filters </li></ul><ul><li>New filter options </li></ul><ul><ul><li>Current user </li></ul></ul><ul><ul><li>Special date values – Next X days, Last Week etc </li></ul></ul>
  12. 12. Approval Process Automation <ul><li>Define simple or multi-step approval processes for any object </li></ul><ul><li>Specify actions at each step of process </li></ul><ul><li>Send approval requests to a queue </li></ul><ul><li>Define one or more user hierarchies for approval request routing </li></ul>
  13. 13. Approvals Demo PTO Request
  14. 14. Sample Approval Process
  15. 15. Anatomy of an Approval Process <ul><li>Process Definition (Global Characteristics) </li></ul><ul><ul><li>Entry Criteria </li></ul></ul><ul><ul><li>Email Template Sent to Approvers </li></ul></ul><ul><ul><li>Record Editability During Approval </li></ul></ul><ul><ul><li>Approval Page Layout </li></ul></ul><ul><ul><li>Approval Page Accessibility </li></ul></ul><ul><ul><li>Allowed Submitters </li></ul></ul>
  16. 16. Anatomy of an Approval Process <ul><li>Initial Submission Actions (Workflow Actions) </li></ul><ul><ul><li>Lock the Record </li></ul></ul><ul><ul><li>Change Field Values </li></ul></ul><ul><ul><li>Send Notification </li></ul></ul>
  17. 17. Anatomy of an Approval Process <ul><li>Step Definition (Decision Criteria & Approval Assignment) (1+) </li></ul><ul><ul><li>Optional Decision Criteria </li></ul></ul><ul><ul><li>Auto-Approve / Reject </li></ul></ul><ul><ul><li>Assign Approver </li></ul></ul><ul><ul><li>Allow Delegated Approval? </li></ul></ul><ul><ul><li>Rejection Behavior </li></ul></ul>
  18. 18. Anatomy of an Approval Process <ul><li>Final Rejection Actions (Workflow Actions) </li></ul><ul><ul><li>Unlock Record </li></ul></ul><ul><ul><li>Change Field Values </li></ul></ul><ul><ul><li>Send Notification </li></ul></ul>
  19. 19. Anatomy of an Approval Process <ul><li>Final Approval Actions (Workflow Actions) </li></ul><ul><ul><li>Keep Record Locked </li></ul></ul><ul><ul><li>Change Field Values </li></ul></ul><ul><ul><li>Send Notification </li></ul></ul><ul><ul><li>Integrate w/ External System </li></ul></ul>
  20. 20. PTO Request – The Finished Product
  21. 21. Summary of Key Features <ul><li>New Workflow Action: Field Update – Automatically change the value in a field as a result of a workflow trigger, including owner and record type! Use Formula Editor wherever applicable to derive value from other fields, expressions, or values. </li></ul><ul><li>New Workflow Action: Outbound API Message – Send a customizable XML message to any desired Web-available listener. No more polling for changes! Use it to update dependent records </li></ul><ul><li>Approval Process Automation – Create simple or multi-step approval processes to automate and enforce the approval of virtually anything in your company, from sales discount requests, to expense reports, to vacation requests. </li></ul>
  22. 22. Varadarajan Rajaram Sr. Product Manager QUESTION & ANSWER Steve Tamm Technical Architect
  23. 23. Approvals API <ul><li>New API – process </li></ul><ul><li>Syntax </li></ul><ul><ul><li>ProcessResult[] = sfdc.process([ProcessRequest[]) </li></ul></ul><ul><li>ProcessRequest </li></ul><ul><ul><li>ProcessSubmitRequest: Submit a record for approval </li></ul></ul><ul><ul><li>ProcessWorkitemRequest: Approve or Reject an approval request </li></ul></ul>
  24. 24. Approvals API <ul><li>Access to approval history and requests through new objects </li></ul><ul><ul><li>ProcessInstanceStep </li></ul></ul><ul><ul><ul><li>The contents of the approval history for a given approval process. </li></ul></ul></ul><ul><ul><li>ProcessInstanceWorkitem </li></ul></ul><ul><ul><ul><li>The current approval requests assigned to a user </li></ul></ul></ul><ul><ul><ul><li>Update this record to reassign workitems. </li></ul></ul></ul>
  25. 25. Approvals API - ProcessRequest Name Type Description objectId ID For submitting an item for Approval, can be the ID of any record with approval processes defined. workitemId ID For submitting an item for processing after approval, the Id of the ProcessInstanceWorkitem. action String For approving or rejecting a workitem for processing, a string representing the kind of action to take: Approve, Reject, or Remove. nextActorIds String[] If the approval request requires the user to select the approver, specify the user ID of the next approver here comments String Any comments to be stored with the approval action in the approval history
  26. 26. Approvals API – ProcessResult Name Type Description entityId ID Object being processed Errors Error[] Set of errors instanceId ID The ID of the ProcessInstance InstanceStatus String The status of the current process instance: “Approved,” “Rejected,” “Removed,” “Started,” or “Pending” newWorkitemIds ID[] The IDs of the newly created approval requests, if any Success boolean “ True” if the approval completed successfully
  27. 27. Sample Code public ProcessResult[] doProcessSample(String comments, String id, String[] approverIds) throws ApiFault {         ProcessResult[] processResults;         ProcessSubmitRequest request = new ProcessSubmitRequest();         request.setComments(comments);         request.setNextApproverIds(approverIds);         request.setObjectId(id);         try {             PartnerConnection connection = Connector.newConnection(xconfig);             //calling process on the approval submission             processResults = connection.process(new ProcessSubmitRequest[]{request});             for (ProcessResult processResult : processResults) {                     if(processResult.getSuccess()){                         if(xconfig.isTraceMessage()){                             log.debug(&quot;Approval submitted for: &quot; + id + &quot;, approverIds: &quot; + approverIds.toString() + &quot; successful.&quot;);                             log.debug(&quot;Process Instance Status: &quot; + processResult.getInstanceStatus());                          }                     } else{                         log.error(&quot;Approval submitted for: &quot; + id + &quot;, approverIds: &quot; + approverIds.toString() + &quot; FAILED.&quot;);                         log.error(&quot;ERRORS: &quot; + processResult.getErrors().toString());                      }             }         } catch (ConnectionException ce) {             ApiFault fault = getApiFault(ce);             ce.printStackTrace();             throw fault;         }         return processResults;     }
  28. 28. Additional Resources <ul><li>“ Tips and Tricks for Advanced Workflow” Tuesday 3:45PM </li></ul><ul><ul><li>See how 144 Workflow helps Deutsche Bank reduce costs and increase efficiency </li></ul></ul><ul><li>Join ADN! </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Documents, toolkits, discussion boards and more! </li></ul></ul>
  29. 29. Session Feedback Let us know how we’re doing! <ul><li>Please score the session from 5 to 1 (5=excellent,1=needs improvement) on the following categories: </li></ul><ul><ul><li>Overall rating of the session </li></ul></ul><ul><ul><li>Quality of content </li></ul></ul><ul><ul><li>Strength of presentation delivery </li></ul></ul><ul><ul><li>Relevance of the session to your organization </li></ul></ul>Save time! Use your cell phone or mobile device to send Feedback via SMS/Text Messaging! Send a message to 26335 In the message body: Session 239, #### For example, “ Session 123, 5555 ” Session ID: 239 Session ID # Scores for 4 categories SMS Voting powered by: