Difference between revisions of "OS.bee Signature Pad"
From OS.bee documentation
(→new entity) |
(→new entity) |
||
Line 39: | Line 39: | ||
#* '''Company''': which company using this slide. | #* '''Company''': which company using this slide. | ||
# new properties and references in entity Mcompany: | # new properties and references in entity Mcompany: | ||
− | <syntaxhighlight lang="java"> | + | #:<syntaxhighlight lang="java"> |
entity Mcompany extends BaseUUID { | entity Mcompany extends BaseUUID { | ||
. . . | . . . | ||
Line 48: | Line 48: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
+ | #* '''signingImage''': save the signing image as a blobmapping data. signingImage is the image which will be displayed on signature pad when customer signes. | ||
+ | #* '''slideDelay''': define the time delay for changing advertising slide image, unit is ms, and this value should be between 1000 and 10000, which means the delay should be between 1 second and 10 seconds. | ||
+ | #* '''Slides''': define a set of advertisingSlides for this company. These advertising slide images will be displayed one after another on the signature pad when no actions on it. | ||
− | + | The detail of entity Mcompany can be set in the following page: | |
− | : | + | In menu--> Master data-->Company: |
− | : | + |
Revision as of 08:14, 5 April 2018
Contents
Signature Pad
Using signature pad for payment process is a new cash payment method.
Basic Functionalities
Basic functionalities of display on signature pad are:
- Show the advertising slide images on signature pad one after another according to de slide delay predefined in Mcompany( in our example, for company FoodMart, the slide delay is defined as 2000, which means 2 seconds).
- When the customer signature is required, the display image on the signature pad will switch to the signing image, additional 3 buttons will be shown under the signing image: done, cancle and delete.(these labels could be translated with I18n)
= Functionalities after signing
The following image is the signing image in our example.
- Customer signs, and then select “done”, the signature of customer will be saved as a blob-mapping data, saving as thousands of points with x,y, pressure... the display of signature pad switch to the advertising slide images.
- Customer signs, and then select “cancle”, the signature process will be broken, switch to the advertising slide images.
- Customer signs, and then select “clear”, the signature will be deleted, and waiting for the next action of customer.
Technical changes in DSL model
new entity
- new entity AdvertisingSlide :
entity AdvertisingSlide extends BaseUUID { persistenceUnit "businessdata" domainKey String slide var Date showFrom properties( key="Date" value="Minute") var Date showUntil properties(key="Date" value="Minute") var BlobMapping image ref Mcompany company opposite slides }
- slide: name of this slide.
- ShowFrom and showUntil: valid date interval for this slide.
- Image: save this slide as a blobmapping data.
- Company: which company using this slide.
- new properties and references in entity Mcompany:
entity Mcompany extends BaseUUID { . . . var BlobMapping signingImage var int slideDelay properties(key="Slider" value="1000:10000") ref AdvertisingSlide[*] slides opposite company properties( key = "Table" value = "" ) . . . }
- signingImage: save the signing image as a blobmapping data. signingImage is the image which will be displayed on signature pad when customer signes.
- slideDelay: define the time delay for changing advertising slide image, unit is ms, and this value should be between 1000 and 10000, which means the delay should be between 1 second and 10 seconds.
- Slides: define a set of advertisingSlides for this company. These advertising slide images will be displayed one after another on the signature pad when no actions on it.
The detail of entity Mcompany can be set in the following page: In menu--> Master data-->Company: