Today, in our business environment, we ship orders to our customers within our ERP system. I have developed a number of what we call Certificates of Validation which are forms that we send with the shipment of all of the serial numbers of the units in the box. Today our users go into Crystal Enterprise after they ship the order in our system and print out certificates by entering the order number. What I have been asked to do is to have this now happen automatically (print the certificates out automatically)rather than have a user have to go into CE and schedule the report. What has been happening is that the user may enter the wrong order and ship out the wrong cert or may choose someone else's certificate because more than one user is running these. In CE9 there is no way of limiting seeing only a particular user's instances (at least I don't think there is) but XI has this functionality I am pretty sure.
So what I was thinking is that when the order actually ships in our ERP system it's status changes. So I could write a trigger in Transact-SQL that writes that order to a table as soon as the status changes, indicating it has shipped. I could then have a certificate report out there that will run based on the existence of a file and that file will only exist if there is anything in the table that I mentioned previously. Then I will clean out the table and delete the file after it has printed.
This is just a first pass of thinking about it and I'm sure there is more to it. But I am interested in hearing from anyone who has implemented anything along these lines.
So what I was thinking is that when the order actually ships in our ERP system it's status changes. So I could write a trigger in Transact-SQL that writes that order to a table as soon as the status changes, indicating it has shipped. I could then have a certificate report out there that will run based on the existence of a file and that file will only exist if there is anything in the table that I mentioned previously. Then I will clean out the table and delete the file after it has printed.
This is just a first pass of thinking about it and I'm sure there is more to it. But I am interested in hearing from anyone who has implemented anything along these lines.