IPIDs are created along with our policy documents and they are appearing in the ODC print queue correctly alongside the policy documents to which they refer. However when we print out a batch of documents (say an entire days renewals), the IPIDs print out in the wrong order / out of sequence. EG A motor policy may have home IPID document printed in the middle of the letters, renewal schedules for that client or a home policy may have a motor IPID printed within it. This then means that we need to go through all the documents (there could be 000's) and manually slot the right IPID into the right policy type. Surely if an IPID is created alongside a renewal, it should print it correctly as a single set of documents. We have tried changing our printer spool settings but it hasn't helped. I cant work out if this is an ODC Issue, an OPM issue, a printer driver issue or a process issue. Any ideas ? Has anybody else experienced this ?
Hi Val - I've not heard this being an issue generally - very strange. OGI will be best to investigate. Would be good to know the outcome!!
Just a thought - is it only the extract / csv with the issue - or does the full printed report still not report these?
Has anyone else come across this problem, we are getting quite a few cases where the renewal is not populating on the list. OGI have been looking at this from the copy CSV lists we have sent them, but have not resolved this issue yet.
Partnership deals that are in the interests of Open-GI's profits and not the best infrastructure for their clients.
HP - (30% returns from printers to servers when I worked for a HP partner. Haven't been pleasantly surprised with 6 more years of dealing with their hardware).
Microsoft - Oh ook another 60 security holes and a zero-day (M$ product zero-days can only be fixed or mitigated by Microsoft) that has been actively exploited for over two months now.
Sophos - Tavis Ormandy of Google's top security team, charitably wrote a 30 page paper, which concludes that the company was "working with good intentions" but is "ill-equipped to handle the output of one co-operative security researcher working in his spare time". Recently, they forced through Multi-Factor Authentication for their "cloud" management site (which has a really useless, coutnerintuitve and uninformative interface), that is completely useless in a ransomware take over, you could easily be left without access to your "cloud". They should implement physical keys if they are going to push for this, not software methods that can be taken over as part of an attack.
Question
John Tasker
IPIDs are created along with our policy documents and they are appearing in the ODC print queue correctly alongside the policy documents to which they refer. However when we print out a batch of documents (say an entire days renewals), the IPIDs print out in the wrong order / out of sequence. EG A motor policy may have home IPID document printed in the middle of the letters, renewal schedules for that client or a home policy may have a motor IPID printed within it. This then means that we need to go through all the documents (there could be 000's) and manually slot the right IPID into the right policy type. Surely if an IPID is created alongside a renewal, it should print it correctly as a single set of documents. We have tried changing our printer spool settings but it hasn't helped. I cant work out if this is an ODC Issue, an OPM issue, a printer driver issue or a process issue. Any ideas ? Has anybody else experienced this ?
Link to comment
4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now