Using Multiple Commands in a Single Template - InfoPath Dev
in

InfoPath Dev

Using Multiple Commands in a Single Template

Last post 11-16-2011 09:34 AM by christian84. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 11-14-2011 02:47 PM

    Using Multiple Commands in a Single Template

    Hello, I am new to qRules and have a pending PO to purchase the full version but for the time being I am running the Trial version. I have seached the forum and read the documentation but could not find the answer. I know that it is possible to use multiple qRules commands since the Sample form does exactly that. My question is; how can I run multiple rules or commands on a single form? For instance, I would like to use DateDiff and some other functions to accomplish a reasonably difficult goal. I would like to have an InfoPath form as content type for a Sharepoint calendar list. This content type would be a work order. The form would create  or modify the corresponding calendar entry and based on the selections in the work order I would like to have sharepoint look for (and create if not availible) customer folders. Within those folders I would like to create usage reports automatically (One for each day) following a specific naming format (which is done). These forms would then, on the modification of the last form, create a summary form and merge all the ther other documents into it. My thoughts were to use a work flow with a variable based on the DateDiff to determine the number of forms to create and in each of the forms to have a field which corresponds to the day number. The work flow would check continuously and once the form with the last number has its status set to modified and the modified date is equal to or greated then the last date of the visit to have the workflow create a summary document and merge all the others into it.

  • 11-16-2011 04:08 AM In reply to

    Re: Using Multiple Commands in a Single Template

     Hi,

    A few of us have read your message but we can't quite understand the scenario. Would you mind rephrasing the question? If you think attachments would help explain the scenario, feel free to use the Options tab to attach files or screenshots. Thanks.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 11-16-2011 08:53 AM In reply to

    Re: Using Multiple Commands in a Single Template

    OK, Im not too good at describing problems ;) I followed the instructions for qrules to add a DateDiff field. This worked. However, when I tried to create another rule item like Weekday I was unable to. I looked at the secondary data source for qrules and everytnig is locked. In the sample form, there are instances for each rule and the data sources are not locked. Is it possible to create a form that has multiple qrules with the trial verson?

  • 11-16-2011 09:04 AM In reply to

    Re: Using Multiple Commands in a Single Template

    I think your question has more to do with how qRules is used.

    When you use qRules, you are setting the Command node to one of the qRules commands. This generates a value in Result. You can use rules to place that Result anywhere you need it.

    Then you execute another command, that is, you set the Command node to some other qRules command. Then this returns another value in Result, and you can use rules to place that Result elsewhere in the form.

    So yes, the qRules secondary data source remains locked - it is locked in the sample form too. If you need extra fields, you add them in the main data source. 

    Hope this helps.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


  • 11-16-2011 09:34 AM In reply to

    Re: Using Multiple Commands in a Single Template

    Got it :) That makes a lot more sence now! I think my problem was where I was putting the rules.

Page 1 of 1 (5 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.