SoftPro Developer Forum

Based on your comment with the watermark in the print pipeline, we were able to work something out to get this to work. One of my guys wrote up some code. It doesn't contain all the code to tie into the print pipeline, but hopefully someone will find it useful. public class TestPrintJobItem : PrintJ...

When distributing a document via the document tree UI, there's an option to add a Stamp (Confidential, Estimated, Draft, ProForma, etc).

Is there a way to do the same thing when rendering the doc through the API? If so, can we see a small code snippet?

Thanks.

Understood that reprinting is beyond the scope of the forums, but what about just posting and printing checks? If we post a check transaction, it doesn't print, and it doesn't pull in the check number into the transaction reference number field. Are you saying standard check printing is also out of ...

Are there any restrictions to adding tags to IOrderItem objects? I'm running into an issue with adding a tag on an item of type "AdditionalTax". IEnumerable<dynamic> SpTaxes = DOrder.Properties[0].Taxes; dynamic ac = Order.CreateNew("AdditionalTax"); ac.Description = "A Tax&...

In the UI on several screens, such as the Tax calculation screens, you can pick “next available” line to have information automatically pushed to the HUD/CDF. Is there a way to trigger this same behavior through the API? While I understand we can just find the next line with no description and add t...

I wasn't able to locate a permissions-based approach either through SPAdmin or the online FAQ (though I might have missed it), so I'm posting to see if there's a programmatic solution. If there is, in fact, a non-programmatic way, any guidance would be appreciated. We'd like to be able to control ho...

Whenever a check is voided in the register, it creates a new pending transaction record for the check. Using information from the new check, is there an easy with to find the original voided check through the API? Even if someone canceled the check 10 times, I'd like to know how to track back to tha...

I could see that for something we're adding new, but we saw the same behavior with changing the lookup code on an existing requirement. We also tried an IOrderItem.Reset on the lookup code before repopulating it, but saw no change in behavior. It still had the squigglies, without pulling in the fiel...

I'm trying to modify or add requirements to Schedule B on a commitment through the API, and the lookup codes we're using has a field code reference in it, e.g. {{Order.Sellers.Name}} When I try this through the UI, it works correctly and pulls in the seller name. However, when doing this through the...

Whatever the fix is, it would be cool to have this hyperlink behavior as an option -- we just don't want it 99% of the time.

Any ideas which release this fix is scheduled for?