-
Hi - You might try some form open rules - switch the view for the conditions that the user's role is Supervisor and status (or whatever the field is) equals approved. In IP 2010, form open rules are on the Data tab in the ribbon - in 2007, I think you have to go to Tools / Form Options to get to them.
-
I would think you could use the original custom pattern and just change to using a substring of the start time - I'm attaching your sample with this modification. Save it locally, right click and select Design to open in design mode and you can see how I've changed that condition on both start and end time. As to your other question - if a ...
-
We are happy to help and so glad you are loving qRules. I'm glad you have everything working the way you want!
-
Hi - I think since this is working for you in Preview but failing in IPFS the most likely culprit is event bubbling. Changes in your nested group are likely causing rules on the parent group to fire again.
In these cases, I usually add some helper fields for rule conditions - normally to a secondary XML file data source. The first rule on my ...
-
The error occurs when we try to set the inner XML of the destination node to the inner XML of the source - my guess is going to be because actual rich text has tags and the string representation in your source data does not - I tried this with a different owssvr.dll data source with the same result. I'm afraid this is likely just not going to ...
-
Yup - I grabbed your sample. I'm going to run this in debug real quick and see what's up - more soon.
-
I'm confused again. You are copying to field4 in your command, but in your screenshot showing the data type for field1.
-
Okay - so, for your Delete command, you'll want to use a concat statement - since you have nested repeating data, your Delete command would actually delete all instances of Truck. Try this instead:concat("Delete /xpath=/my:myFields/my:Shippings/my:Shipping[", count(preceding-sibling::my:Shipping) + 1, ...
-
So - what does "doesn't work" mean here? Rows not inserted at all? Rows inserted in the wrong place? Can you put the QdabraRules error node on your form and see if you get an error back? I'll take a quick look at your form.
-
Okay - looks like there is a difference in the XML, at least between 2007 & 2013 (my 2010 VM is feeling a bit sulky this morning). In 2013, the rules aren't firing because the pattern condition isn't being met - the time now includes the UTC offset (see attached screenshot). I removed the custom pattern requirement and the rule ...