Hi, this could help. Thanks.
Hi,If you can add an additional parameter in your report that will tell which layout to print and set it in a report schema variable. Then you can create separate Report rules as mentioned in answer by @Kelum Pradeep KumaraYou can add report rules conditions with this schema variable to select different layout by default. Thanks.
Hi @Corc22 I know I am too late, but If I am understanding your requirement correctly, you need a persistent field with a default value set using a ‘SELECT...’ statement, am I right?If this is the case, you can set Default Value when you create a persistent field. Select a ‘PLSQL Expression’ and type your SELECT statement - Thanks.
Hi,You can add another report rule with “Route to Connect”, or in the same rule but another action.Then you can setup Routing Rules, Routing Address and FILE_SENDER, to upload the file on the shared repository.We had same kind of requirement but we needed it on FTP server, so we used FTP_SENDER.More details about the solution can be found here - Thanks.
Hi,We had a same requirement.When we use the report rule “Check in to Document management” and the Doc Class is of type “FTP”, then the PDF report generated gets attached on the screen but not sent to FTP. As Mathias said, FTP is not an option here.Since it was not working, we added another report rule “Route to connect”, and then setup the Routing Rule, Routing Address and FTP Connector.With this, we were able to automate the transfer of PDF invoices to the FTP server. Note :- We had to follow the same naming convention as in IFS Docman. More detail can be found here - Although there could be some bugs in this solution because we have to generate the same file name as Docman generated for the current invoice. We didn’t use the Doc_Seq_no Sequence, because its CURRVAL is session dependent, we used an SQL query instead. Thanks.
We got access to a fraction of FTP logs that shows how 2 file uploads to FTP are continuously looping.We still can’t figure out what caused them to go in loop in the first place. We checked our Application messages, the file ending with 1000579-1-A1-1.PDF was initiated on 5th Jan’ 22 and the other file 1000584-1-A1-1.PDF was initiated on 6th Jan’ 22. We couldn’t get hands on the logs of 5th and 6th Jan yet, so we can’t figure what was the root cause of this loop. Anyways, my question is still same, how can we limit this solution to execute for a Max no. of retries only.
I can’t think of a way to show the previous page total at the top of the next page if the record counts per page are dynamic. You could do a running total using sum and partition by either as a custom field or in your report code. And you could show the running total for the previous record using lag or by subtracting the current record from the running total. But I don’t know how you’d make that appear only once at the top of the new page. Do your description lengths vary so much that you can’t create groups of records with subtotals? Yes Tracy, the lengths of the descriptions are totally unpredictable. They can take 1 or more lines. If I make an ‘x’ number of lines items as a group, I won’t be sure that they will fit in one page.
Can you put the altered layout on the First Page and use the Repeating page for the full layout? Hi Tracy, Thanks for replying.The field is actually on the Page body “Flow area”, which remains the same for First, Repeat and Last Page. I guess we cannot have different page body in First, Repeat and Last ?!The field is on a line-item table and will be used to calculate the sum of amounts on previous pages.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.