Anatomy of a Splatforms Task

Posted on December 2, 2010
Filed Under Splatforms | 6 Comments | Share this post via splatforms.com

The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated assistance, and then we take that form data and do all kinds of “stuff” with it. That “stuff” that is done using that data gets done by running Tasks. While the underlying infrastructure is the heart and soul of the splatforms.com operation, it is the individual Tasks that actually provide the value. Without the individual Tasks, the underlying infrastructure is just useless plumbing without a purpose.

But what, exactly, is a Task? Conceptually, a Task is the sheet music that dictates the way in which the various steps will be orchestrated to accomplish a specific goal. Tasks have names like “Post an Event on your Google calendar” or “Share a Link on Plurk.” They are created to do one specific thing, for one specific kind of *form, on one specific target web site. Physically, a Task is a collection of properties that defines what is to be accomplished, and how it is to be accomplished. It is the “rules” for getting one thing done. When you set up your preferences, you pick and choose from all of the available Tasks to create a complete list of all of the things that you want done whenever you submit a certain kind of *form. From then on, you fill out the *form once, and then all of the stuff that you have selected gets done.

A Task has three basic components: 1) general information about the Task, 2) a list of one or more “steps” that will be carried out to complete the Task, and 3) for every step, a list of one or more evaluations that will be used to determine the outcome of each step after it has been carried out by the *forms Local Agent. A Task can be represented in XML, such as this simple one-step Task to post a link on Tumblr:

<task id="26">
  <name>Post Link as Tumblr blog entry</name>
  <description>Posts your link to Tumblr as a blog entry</description>
  <status>b</status>
  <author id="37">jtasker</author>
  <type id="l" code="link">Link</type>
  <site id="12" code="tumblr">Tumblr</site>
  <credSite/>
  <created>2010-08-05 23:51:21</created>
  <lastUpdated>2010-08-06 09:39:34</lastUpdated>
  <steps>
    <step number="1">
      <hangTime>0</hangTime>
      <method>post</method>
      <url>http://www.tumblr.com/api/write</url>
      <parameters>email=$!username
password=$!password
type=link
name=$!title
description=$!comments
url=$!url
generator=Tumblr Link Post by Joe Tasker via splatforms.com
private=#if($privacy==1)0#{else}1#end

tags=$!tags
format=markdown</parameters>
      <headers></headers>
      <evaluateResponse>
        <eval number="1">
          <type>1</type>
          <area>2</area>
          <required>0</required>
          <patternExpression>201</patternExpression>
          <fieldName></fieldName>
          <whenTrue>
            <outcome>1</outcome>
            <qualifier>0</qualifier>
          </whenTrue>
          <whenFalse>
            <outcome>0</outcome>
            <qualifier>0</qualifier>
          </whenFalse>
        </eval>
        <eval number="2">
          <type>1</type>
          <area>2</area>
          <required>0</required>
          <patternExpression>403</patternExpression>
          <fieldName></fieldName>
          <whenTrue>
            <outcome>2</outcome>
            <qualifier>10</qualifier>
          </whenTrue>
          <whenFalse>
            <outcome>0</outcome>
            <qualifier>0</qualifier>
          </whenFalse>
        </eval>
        <eval number="3">
          <type>1</type>
          <area>2</area>
          <required>0</required>
          <patternExpression>400</patternExpression>
          <fieldName></fieldName>
          <whenTrue>
            <outcome>2</outcome>
            <qualifier>24</qualifier>
          </whenTrue>
          <whenFalse>
            <outcome>2</outcome>
            <qualifier>19</qualifier>
          </whenFalse>
        </eval>
      </evaluateResponse>
    </step>
  </steps>
</task>

This Task has one step, and that step has three evaluations that take place, which in this particular case all happen to look at the HTTP Response Code for specific values as laid out in the Tumblr API. Every Task is unique, but they are based on the same basic structure, made up of the basic definition, the steps, and the evaluation criteria for each step. Because we have opened up the Task creation process to Third-party developers, virtually anyone can create a Task of their own choosing and add it to pile.

Maybe you’d like to give it a try!

Comments

6 Responses to “Anatomy of a Splatforms Task”

  1. pligg.com on December 2nd, 2010 12:48 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated ass……

  2. pligg.com on December 2nd, 2010 12:50 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated assistance, and then we take that form data do all kinds of “stuff” with it. That “stuf…

  3. SERPD on December 2nd, 2010 1:17 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated assistance, and then we take that form data do all ki……

  4. socialwebcms.com on December 2nd, 2010 3:27 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated ass…

  5. 10url.com on December 2nd, 2010 3:37 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated ass…

  6. lifeinnews.com on December 2nd, 2010 3:37 pm

    Anatomy of a Splatforms Task…

    The concept behind splatforms.com is pretty simple, really: you fill out a simple form, either manually or with the help of some kind of automated assistance, and then we take that form data do all kinds of “stuff” with it. That “stuf…