Are you talking about a dynamic action or a process on page submit? Because we'd be looking at different things.

Page submit would be looking at the source fields, or this property for DAs

Submit sends your value from browser to DB, for PL/SQL processing. Return sends any updated session state value back to the browser field.

Since you have apex_error, I'm guessing page submit? If so, maybe you need to detail your scenario more.

Yes, page submit (Process tab)

In that case, it's all about where your item is getting the value to be displayed, in the source attributes.

And do you have an item called 120_MY_TEXTAREA, or P120_MY_TEXTAREA ?

Just confirming, since general convention prefixes all page items with P.

So you need to assess how that's being sourced, and if there are any computations.

Fabrizio Delli Priscoli wrote:

 

I assign value to this textarea item during process and values that I assign to this textarea item are displayed only when the process is finished, while I want to "force" refreshing of the textarea item directly from process, when a call to my database package is finished and before I make a new call to database package.

This is effectively the same scenario as that in your previous question: show a confirmation message in a process

Communication between server programs and the client browser during page accept processing is not supported out of the box. This type of push notification requires the use of WebSockets (which can be implemented using Node.js: https://jsao.io/2015/02/real-time-data-with-node-js-socket-io-and-oracle-database/) or Server Sent Events (which has significant compatibility issues thanks to one particular browser vendor...)

Fabrizio Delli Priscoli wrote:

 

I assign value to this textarea item during process and values that I assign to this textarea item are displayed only when the process is finished, while I want to "force" refreshing of the textarea item directly from process, when a call to my database package is finished and before I make a new call to database package.

How long does this processing take?

Fabrizio Delli Priscoli wrote:

 

about 20 minutes

There are two problems with that:

1. There is a strong possibility that the request will be timed out, leaving the user with an error or a blank page.
2. Users generally don't want to be sitting waiting for something to happen for 20 seconds, let alone 20 minutes.

I have on a page a textarea item in which I want to show all the points of my process.

I have a button that recall a page process, a PL/SQL code process, in which I make many recalls to a database package.

What I want is that between a package call I assign a value to my textarea item and it is refreshed.

Is it possible ? Or in case is not possible is there a way to achieve this?

Thanks all for collaboration,

Fabrizio

 

Here is example of my PL/SQL page process:

 

 

:120_MY_TEXTAREA := 'FIRST CALL TO PACKAGE'||chr(10);

MY_PACKAGE.MY_PROCEDURE_1(:p120_year,:p120_month);

if SQLCODE = 0 then

:120_MY_TEXTAREA := :120_MY_TEXTAREA||'SECOND CALL TO PACKAGE'||chr(10);

MY_PACKAGE.MY_PROCEDURE_2(:p120_year,:p120_month);

else

apex_error.add_error(p_message  =>'ERROR OCCURS: '||SQLERRM,p_display_location =>apex_error.c_on_error_page);

end if;

 

and so on....

Instead of executing these programs directly from APEX, I would use the following alternative approach to perform the required processing in the background as a scheduled job, enabling users to continue working in the application whilst it is running.

• The package API methods involved are defined as scheduler programs, and the overall workflow implemented using a chain.
• The after submit page process creates an instance of the job scheduled to start immediately, and provides the user with the unique job name.
• Job progress and status is tracked using the appropriate data dictionary scheduler views:
  • USER_SCHEDULER_JOBS
  • USER_SCHEDULER_JOB_RUN_DETAILS
  • USER_SCHEDULER_RUNNING_JOBS
  • USER_SCHEDULER_RUNNING_CHAINS
• Users can be emailed when the job is completed or fails.
• The application can provide feedback to users on the progress and status of their jobs in various ways:
  • Reports
  • Conditionally displaying Alert regions on page show
  • Icons and badges in menu and navigation bar entries