# INPUT after PROCCESS PAGE MODAL

**URL:** <https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, NaturalONE, Natural-for-AJAX\
**Created:** [February 1, 2018, 6:18pm UTC](https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982 "2018-02-01T18:18:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Fabio\_Maturano](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@Fabio\_Maturano](https://techcommunity.softwareag.com/u/Fabio_Maturano)\
**Post date:** [February 1, 2018, 6:18pm UTC](https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982/1 "2018-02-01T18:18:00Z")

</div>

Hi everyone.

I’ve been facing lately a issue on natural for ajax since my company moved from natural for mainframe to natural for linux.

After a PROCCESS PAGE MODAL, we have a call to INPUT, passing some parameters, like shown on picture 1. This code was working just fine on natural for mainframe.

However, after the move to linux, the error shown on pictures number 2 and 3 is raired.

Is that a expected behaviour? I am really thankful if there are any answers on this matter.

Thanks in advance.  
 ![picture1.PNG](https://global.discourse-cdn.com/techcommunity/original/2X/b/b3c5ad6fe928d07c76d2b0731c023164ae720f47.png)

 ![picture2.PNG](https://global.discourse-cdn.com/techcommunity/original/2X/9/9386b4f590f18147a965e0b965098394a68679fb.png)

---

<div class="post-metadata">

**Author:** ![Fabio\_Maturano](https://avatars.discourse-cdn.com/v4/letter/f/e36b37/32.png) [@Fabio\_Maturano](https://techcommunity.softwareag.com/u/Fabio_Maturano)\
**Post date:** [February 1, 2018, 6:19pm UTC](https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982/2 "2018-02-01T18:19:10Z")

</div>

Here goes picture3

 ![picture3.PNG](https://global.discourse-cdn.com/techcommunity/original/2X/7/7156206573b7f4c09ead8f015613c415ffbac289.png)

---

<div class="post-metadata">

**Author:** ![Todd\_Beckwith1](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@Todd\_Beckwith1](https://techcommunity.softwareag.com/u/Todd_Beckwith1)\
**Post date:** [February 10, 2018, 6:30pm UTC](https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982/3 "2018-02-10T18:30:09Z")

</div>

Fabio,

I’ve seen issues similar to this in the past. After displaying the pop up, you should always return to the base page before displaying something else. To accomplish what you want to do, you may need to leverage NJX:TRIGGEREVENT so that once you reprocess the base page, you immediately fall out of it and can perform addition processing in Natural.

The remainder of this post is from NJX documentation on the NJX:TRIGGEREVENT from [http://techcommunity.softwareag.com/ecosystem/documentation/natural/njx834/njx/njx\_triggerevent.htm?hi=modal](http://techcommunity.softwareag.com/ecosystem/documentation/natural/njx834/njx/njx_triggerevent.htm?hi=modal)

> [@](#):
>
> Examples  
> Common usage scenarios for the NJX:TRIGGEREVENT control are scenarios in which the event reaction of your Natural application consists of several parts which contain data handling and page navigation or pop-up handling. Triggering an event allows you to modularize and combine these different event reaction parts. Some specific sample use cases are described below.
> 
> Pop-ups  
> Your application might want to navigate to a specific page when a pop-up is closed. The navigation may depend on some return value of the pop-up. When the pop-up is closed, the Natural application can trigger an event depending on the pop-up result. In the triggered event, the Natural application can then do the navigation. The following code shows how this can be done:
> 
> ```auto
> DECIDE ON FIRST *PAGE-EVENT
> VALUE U'nat:page.end',U'nat:browser.end'
> /* Page closed.
> IGNORE
> VALUE U'onReactionA'
> FETCH RETURN 'MYPRGA'
> PROCESS PAGE UPDATE FULL
> VALUE U'onReactionB'
> FETCH RETURN 'MYPRGB'
> PROCESS PAGE UPDATE FULL
> VALUE U'onOpenMyPopup'
> PROCESS PAGE MODAL
> CALLNAT 'MYPOPUP' MYRETURN
> END-PROCESS
> IF MYRETURN = 'A' THEN
> XCITRIGGEREVENT:='onReactionA'
> END-IF
> IF MYRETURN = 'B' THEN
> XCITRIGGEREVENT:='onReactionB'
> END-IF
> PROCESS PAGE UPDATE FULL
> NONE VALUE
> /* Unhandled events.
> PROCESS PAGE UPDATE
> END-DECIDE
> ```

I hope this helps.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:40pm UTC](https://techcommunity.softwareag.com/t/input-after-proccess-page-modal/197982/4 "2021-04-02T15:40:03Z")

</div>