-
I don't believe the workflow can really start until the document is committed to the library. It does not commit until it has been checked in once, so I'm not sure you can use the SPD workflow to perform the initial check-in.
-
Well, it only calculates when you tell it to. Form Load rules should have conditions telling them what to do and when.
-
Use rules instead of default values then.
-
Just don't use a date control - use a text control formatted to show time.
-
You found the right place for fixing it, and that is what fixed it for us. I had never seen that problem before until my SP Admin did a repair, which reset some registry permissions. I think he followed Joel Oleson's advice on where to fix the permissions and where to add the App ...
-
I'm confused, because this is _very_ simple and is explained in detail with my blog entries. I'm not sure you've read them yet. You don't need to use some separate XML file. Use the data available to you in the profile database or in a Contacts list.
InfoPath – User Roles in Browser-Enabled Forms Using ...
-
By editing the XSD files?
-
Manu, that seems like a bit much to accomplish this. I don't think it makes sense to administrative approve EVERY form just for this purpose. That's a ton of work and a ton of extra administrative overhead, imo. My method mentioned above is very simple and works perfectly well for both scenarios you gave: workflow ...
-
It's a limitation of SharePoint - it can't do that. However, Qdabra may have a solution for you to do that in the near future.
-
Not two forms, but two views in one form, and we've twice mentioned putting the check boxes in sections that then have conditional formatting to hide them according to their values. I'm not sure if that's what you're repeating or if you're saying something else. Your explanation is unclear, and I'm not sure what ...