Creating Gift Cards with INR value using Groovy script in SAP Hybris

By Ramesh V

In this article, we are going to explore how to create a number of Gift Cards with INR [₹] value using Groovy script in Hybris.


Groovy script to create a Gift Cards with INR [₹] value:

import com.core.model.GiftCardModel;

import com.core.service.giftcard.GiftCardService;

import com.core.enums.GiftCardType;

import com.core.enums.GiftCardSourceSystem;


// Initiate necessary services 

gittCardService = spring.getBean("giftCardService");

userService = spring.getBean("userService");

modelService = spring.getBean("modelService");


int gift_card_count = 10; // Here, pass any number to generate 'n' number of gift cards

double gift_card_amount = 100.0; // INR value of the gift card

var customer_email = 'dummy@gmail.com'; // provided dummy email id and later on we can share this generated gift card with original customer


for (int i = 1; i <= gift_card_count; i++) {

        GiftCardModel giftCardModel = giftCardService.giftCardGenerator(gift_card_amount,                                                     customer_email, GiftCardType.GIFTCARD", GiftCardSourceSystem.SCRIPT);

        giftCardModel.setCreatedBy(userService.getCurrentUser());

        giftCardModel.setCreationReason("Gift Card created for new campaign");

        // Save the gift card

        modelService.save(giftCardModel);

       println giftCardModel.getCode() + ' ' + giftCardModel.getBalanceAmount() + ' ' +                                                                                                 giftCardModel.getCustomerEmailID();

}

println 'No. of Gift Cards created - ' + gift_card_count;

printly 'Script executed successfully!!!'


Outcome:

Gift card code           Amount    Customer Email ID

xxxxxxxxxxxxxxx1,  100.0,        dummy@gmail.com 

xxxxxxxxxxxxxxx2, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx3, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx4, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx5, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx6, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx7, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx8, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxxx9, 100.0,         dummy@gmail.com 

xxxxxxxxxxxxxx10, 100.0,         dummy@gmail.com 



Please feel free to add your comments if you are having any queries.

Location:Hyderabad Hyderabad, Telangana, India
SAP CX Senior Consultant[Hybris]

Comments

Post a Comment

Popular posts from this blog

Type System in SAP Commerce [Hybris]

By Ramesh V
In this article, I have explained in details about what is a Type System in SAP Commerce [Hybris] and how the data can be organized in the Hybris system. Type System in SAP Commerce is a data modeling framework . It defines the structure and organization of data within the platform. In SAP Commerce data can be organized in the form of types , for example product information, customer information, address information, cart information and order information etc. A type is a template for objects and every object stored in a platform is a type instance. Types can be defined in an items.xml file using following aspects: the deployment : It defines the database table where objects stored. attributes : Manage and store data for the object. the java class of the object. In SAP Commerce, Type is a blueprint of an Item and Item is an instance of a Type . Types can inherit from other types, allowing for a hierarchical organization of data. Attributes define the properties of a type. They can ...
Read more

Differences between Extension and AddOn in SAP Hybris

By Ramesh V
In this article, I have explained differences between Extension and AddOn in details in SAP Commerce [Hybris] and also described when to use Extensions and when to use AddOn's. An Extension is a self-contained module that adds or modifies functionality in SAP Commerce.   An Extension generally represents a larger functionality and it contains business logic, type definitions, back-office configurations and other configuration files like xml, properties and etc, whereas AddOns are used to extend the functionality of SAP Commerce Accelerator[storefront] without modifying the core code base. AddOns are plugin kind of extension, you can easily remove your AddOns without refactoring the code of your Accelerator extension. Extension can work independently or extend the another extension whereas AddOn always depends on an existing extension (e.g. acceleratorstorefront). Extensions are used for business logic whereas AddOns are mostly used for Frontend/UI customization.     ...
Read more

items.xml in SAP Commerce [Hybris]

By Ramesh V
The items.xml file specifies types of an extension for defining the data model . By editing the items.xml file, you can define new types or extend existing types. In addition, you can define, override, and extend attributes of the types. Location of the items.xml file: The items.xml is located in the resources directory of an extension. The items.xml files are prefixed with the name of their respective extension in the form of extension name-items.xml. For example: For the core extension, the file will be core-items.xml . For the catalog extension, the file will be catalog-items.xml . Basic structure of the items.xml file: The items.xml defines the types for an extension in XML format and the basic structure is as follows: <items   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"               xsi:noNamespaceSchemaLocation="items.xsd">           ...
Read more