Hi @OrangeCloud 

You might be able to get an idea by referring below 2 threads. Some working examples are given in the comments section.

Hi @OrangeCloud ,

Yes. You can do it through a report rule. In the documentation it mentioned as

Print Dialog shows the default properties and forced properties for a print job. There are several levels of setting up these defaults using actions.

1. Set Default Property
   If you set an action type of Set Default Property it will set pre-selected properties in the action in the Print Dialog. However when the Report Format request is made the Report Formatter will also check for the default properties in the action and will apply these settings which would not override any changed settings from the Print Dialog. These settings may come in use when print jobs are directly sent from application without going through the Print Dialog.
   Documentation link
   Report Rules (ifsworld.com)
   
   Best Regards
   -Kelum

@Kelum Niranjana i cannot open this documents. the URL took me nowhere.Is there a way you can attach its pdf. Thanks

@Randini Jayasundara i studied the linked topics and find out that these are including code along with report rule. We do not want to add code, Is there a way to send Order Confirmation directly to Report Archive and Printer from front end only In IFS10?

We have this report sent out to Report Archive without getting confirmation from user in the form of print dialog in IFS8. our users think this is an additional hassle in IFS10 that is not needed or they are not used to of it.

Hi @OrangeCloud 

Sorry for the delay. 

Is the issue only with printing Customer Order Confirmation? If so I think we can use the Order Type to resolve that.

If the Stop After is unchecked for the RELEASE ORDER event, once the CO is released, the Order Confirmation will be printed without getting the print dialog. However if you use the RMB: Print Order Confirmation in CO header, still you will get the Report Format & Output dialog.

Which service pack was used in IFS8? If it was SP1 (or earlier) then print dialog was not showing when RMB: Print Order Confirmation was clicked. The print dialog for Customer Order Confirmation was introduced via a patch in IFS8 SP2.

@Randini Jayasundara Thanks for replying.
we are on IFS8 SP1 and upgrading to IFS10.
Case on hand is printing Order Confirmation and Instant Invoice with RMB option (especially after releasing credit block from customer order). Accounting don't want to have extra step of waiting and clicking on Print Dialog. They would like the confirmation to be printed after they Release the Credit Check.

you mentioned ‘print dialog for Customer Order Confirmation was introduced via a patch in IFS8 SP2.’ Can we disable it in few of our reports in IFS10? an easy working example will be helpful.

Thanks

Hi @OrangeCloud 

In IFS8 SP2 print dialog for Customer Order Confirmation was introduced as a functional enhancement. Still the functionality has both online and automated options where you can bypass the print dialog by setting up Order Type. If there is no stop until reservations in Order Type, system will automatically send the order confirmation. So it is not recommended to remove the patch (the patch was given only for printing Customer Order Confirmation). Else you can request the change as a customization. Hope this part is clear.

However I understand, in your scenario the Order Type is of no use since the CO is credit blocked. In such case, the CO does not resume Order Type workflow even after releasing the credit check. So you have to use RMB: Print Order Confirmation.

Without going for a customization, you can easily achieve this using a Custom Menu of Action Type PL/SQL Block. I added a custom menu named ‘Quick Print Order Confirmation’ in CO header and PL/SQL Block was written as follows by looking at the examples given in above links. And it worked.

PL/SQL Block

DECLARE

   layout_name_        VARCHAR2(30)  := 'CustomerOrderConfRep.rdl';

   report_id_          VARCHAR2(30)  := 'CUSTOMER_ORDER_CONF_REP';

   report_attr_        VARCHAR2(2000):= '';

   parameter_attr_     VARCHAR2(2000):= '';

   instance_attr_      VARCHAR2(2000):= '';

   print_attr_         VARCHAR2(2000):= '';

   attr_               VARCHAR2(2000):= '';

   distribution_list_  VARCHAR2(2000):= '';

   print_job_id_       VARCHAR2(2000):= '';

   printer_id_         VARCHAR2(2000):= 'No Printout,SERVER,NO_PRINTOUT';

   result_key_         VARCHAR2(2000):= '';

BEGIN

   Client_SYS.Clear_Attr(report_attr_);

   Client_SYS.Add_To_Attr('REPORT_ID',   report_id_,   report_attr_);

   Client_SYS.Add_To_Attr('LAYOUT_NAME', layout_name_, report_attr_);

   Client_SYS.Clear_Attr(parameter_attr_);

   Client_SYS.Add_To_Attr('ORDER_NO', &order_no, parameter_attr_);

   Client_SYS.Clear_Attr(print_attr_);

   Archive_API.New_Client_Report(result_key_, report_attr_, parameter_attr_, distribution_list_, print_attr_); 

   Archive_API.Get_Info(instance_attr_, parameter_attr_, result_key_);

   Client_SYS.Clear_Attr(attr_);

   Client_SYS.Add_To_Attr('PRINTER_ID', printer_id_, attr_);

   Print_Job_API.New(print_job_id_, attr_);

   Client_SYS.Add_To_Attr('PRINT_JOB_ID', print_job_id_, instance_attr_);

   client_SYS.Add_To_Attr('RESULT_KEY',   result_key_,   instance_attr_);

   Print_Job_Contents_API.New_Instance(instance_attr_);

   Print_Job_API.Print(print_job_id_);

END;

Relevant CO No will be assigned to &order_no when the custom menu is clicked. I guess you need to give the relevant Printer ID for printer_id_ variable.

You can create similar custom menus for other reports as well.

Thanks @Randini Jayasundara