cancel
Showing results for 
Search instead for 
Did you mean: 

Background Sending in Agentry apps

Former Member
0 Kudos

Dear SCN,

We have implemented SAP WM 6.2 with Meter Management 2.0 on SMP RT 3.0 SP05. Following SAP note 2281769 (Asynchronous sync option always disabled) we downgraded the SDK to 3.0 SP09.

The business requirement we currently have is to enable background sending at Work Order Start, Edit, Hold, Transfer and Complete. When technicians are out in the field they will have online connectivity and updates on Work Orders need to be transferred back immediately in order to initiate follow-up action or activities.

Background sending is working on Start, Hold and Transfer, but not on Edit or Complete.

Having read pretty much all SCN discussions relating to Background Sending this appears to be as a result of the Update Step in the Transaction, which does not exist on Edit or Complete. For example:


Related to this is the following observation: if you Start the Work Order the background send gets triggered and updates the long text of the Work Order with a status change description. Now Edit the Work Order, for example change description or priority. On Hold these changes are not considered in the background send, however the status/reason change on Hold does get sent. All changed during Edit are only processed during the next manual Transmit

This leads me to the following questions:

1. Why are changes in between Start and Hold not considered in the background send?

2. How can we implement the background send on other transactions like Edit and Complete?

3. Is there perhaps another (better / easier) way to have changes sent automatically?

Regards,
Edwin

Accepted Solutions (0)

Answers (1)

Answers (1)

mark_pe
Active Contributor
0 Kudos

Edwin,

Let us try to answer your questions:

1. Why are changes in between Start and Hold not considered in the background send?


Answer: First of all most of the out of the box ERP/CRM mobile products (Work Manager, Inventory Manager and others) are not designed to be used in Background sending.  A customer will need to fully adjust all the applications steps to be able to do so. Background sending is a special breed of feature that Agentry (design platform) provides. This means either the application was designed from the ground up to use Background sending or not. In your case above, you are just customizing an already designed application. 


It will be required by the user to really study each actions and transactions and transmit flow to make sure it complies with background sending.


Example: A user did 2 actions in the same time.

Action 1:

|____transaction1

|____Apply1 

|____transaction2

|____Apply2  (Click Finish)  - background send 1- data sent to backend

And


Action 2:

|__transaction1

|__transaction2

|__subaction

|__Apply3  (Click Finish) - background send 2 - data sent to backend


Note: If you need the two actions to work together then you need to consider when you press the Finish or else they are two different transmits.  Only a main transmit will follow the order of transmit.


With this said, the definition of background sending is each time you do a transaction (i.e. Apply the property or click Finish in the transaction) it will send the data to the backend.  This means that if you have multiple transactions or actions that have multiple steps for each "Finish" that you introduced it triggers the background send.


2. How can we implement the background send on other transactions like Edit and Complete?


Edits and Complete are different action and transactions as well. So in theory as I said above, unless your application is designed from the ground up as background sending it will be tougher to re-architecture the application.  Normally background sending feature are given to the design team by Agentry as shown in the editor but the theory is, the design team will design an app from scratch (that will utilized this functionality).


3. Is there perhaps another (better / easier) way to have changes sent automatically?


You will need to play with the transmit actions in the editor. There are a few options in there.

But some other consultants may share their experiences.

Best Regards,

SAP Mobile Support Team