Ideas

4 Vote

Web hooks required in Ginesys ERP (PreSave/PostSave)

webhooks (ie. reverse APIs, called on an occurrence event in GINESYS) along with the current vision of a GDS and EMR/API Gateway. This will allow event based integration/validations with 3rd party Apps. Case Study: To integrate with a 3rd Party...

Created 11 Oct 09:25am by Product Team

Third Party Integration

0 Likely to implement
1 Vote

Reflection of Online Sale in analytics view of Stock

No description provided

Created 28 Jul 01:44pm by Product Team

Third Party Integration

0 Planned
1 Vote

POS Return against Online Invoice

No description provided

Created 25 Jul 07:30am by Product Team

Third Party Integration

1 Likely to implement
1 Vote

need getItemStock getItemsStockAtSite API (Fetch)

No description provided

Created 25 Jul 07:28am by Rohit Khetan

Third Party Integration

0 Likely to implement
1 Vote

GDS - Validation for allocation of item in POS should be removed from Online invoice API

No description provided

Created 25 Jun 12:44pm by Product Team

Third Party Integration

0 Likely to implement
1 Vote

GDS: Class Code, Class name to be given for all Outbound events where FINSL is available

No description provided

Created 25 Jun 10:17am by Product Team

Third Party Integration

0 Unlikely to Implement
1 Vote

GDS: Inbound: Scope for deletion of posted invoices

GDS: Inbound: Scope for deletion of Invoices

Created 25 Mar 04:31am by Product Team

Third Party Integration

0 Planned
9 Vote

Customer Easyrewardz Loyalty points accrual restriction flag required while POS bill

We are using Easyrewardz EMR loyalty program, we required Customer Loyalty points accrual restriction flag while making POS bill. Because some times we provide discount to customer that time we don't want to issue loyalty points. But we required c...

Created 27 Feb 06:05am by Clothings .

Third Party Integration

1
5 Vote

EMR: Addition of missing parameters in JSON generation file from EMR sync

Addition of missing parameters in JSON generation file for submission of POS bill in adhoc basis from EMR sync

Created 2 Jan 04:42am by Product Team

Third Party Integration

0 Planned
1 Vote

GDS: Scope for visibility of MS type online sale invoices from Ginesys front end.

Scope for visibility of MS type online sale invoices from Ginesys front end.

Created 20 Dec 10:37am by Product Team

Third Party Integration

0

Note : Do not post a lengthy title for an Idea. Post your Idea clearly supported by Screenshots, Examples and Case Studies (if possible).

Ideas

Filter by status

Filter by category

Web hooks required in Ginesys ERP (PreSave/PostSave)

Reflection of Online Sale in analytics view of Stock

POS Return against Online Invoice

need getItemStock getItemsStockAtSite API (Fetch)

GDS - Validation for allocation of item in POS should be removed from Online invoice API

GDS: Class Code, Class name to be given for all Outbound events where FINSL is available

GDS: Inbound: Scope for deletion of posted invoices

Customer Easyrewardz Loyalty points accrual restriction flag required while POS bill

EMR: Addition of missing parameters in JSON generation file from EMR sync

GDS: Scope for visibility of MS type online sale invoices from Ginesys front end.

Filter by status

Filter by category

Identify yourself with your email address

Web hooks required in Ginesys ERP (PreSave/PostSave)

Reflection of Online Sale in analytics view of Stock

POS Return against Online Invoice

need getItemStock getItemsStockAtSite API (Fetch)

GDS - Validation for allocation of item in POS should be removed from Online invoice API

GDS: Class Code, Class name to be given for all Outbound events where FINSL is available

GDS: Inbound: Scope for deletion of posted invoices

Customer Easyrewardz Loyalty points accrual restriction flag required while POS bill

EMR: Addition of missing parameters in JSON generation file from EMR sync

GDS: Scope for visibility of MS type online sale invoices from Ginesys front end.