Please add another extension point

Here you can put ideas for new functionalities and improvements.

Moderators: rmvanarkel, hugo, alexandre

Post Reply
admin_de2
Posts: 97
Joined: Wed Dec 31, 1969 9:00 pm

Please add another extension point

Post by admin_de2 »

Dear Cyclosians,

for a specific transfer type we want to adapt the transaction value.
The value must not be provided before submitting the transaction, it's always calculated from custom transaction fields.

Since it is not possible to provide a value 0 or no value in transactions, it is neccessary to add another extension point for transactions, which is called before the validation, where the transaction amount can be determined.

We know already the extension points for transaction "Preview" and "Confirm", but this does not meet the requirements: The validation lead to failure since the transaction value cannot be calculated before.

Is it possible to add extension point for transaction "before validation"?

Thank you, Thomas
Attachments
extension-point.png
extension-point.png (68.17 KiB) Viewed 1970 times
shashank
Posts: 7
Joined: Tue May 28, 2019 8:59 am

Re: Please add another extension point

Post by shashank »

admin_de2 wrote: Fri Jul 10, 2020 4:41 am Dear Cyclosians,

for a specific transfer type we want to adapt the transaction value.
The value must not be provided before submitting the transaction, it's always calculated from custom transaction fields.

Since it is not possible to provide a value 0 or no value in transactions, it is neccessary to add another extension point for transactions, which is called before the validation, where the transaction amount can be determined.

We know already the extension points for transaction "Preview" and "Confirm", but this does not meet the requirements: The validation lead to failure since the transaction value cannot be calculated before.

Is it possible to add extension point for transaction "before validation"?

Thank you, Thomas
Hi Thomas,
Just a thought, what happens if you preset a value in amount field and proceed with transaction after that you can change the value in scripts, will that work?

Regards,
Shashank
admin_de2
Posts: 97
Joined: Wed Dec 31, 1969 9:00 pm

Re: Please add another extension point

Post by admin_de2 »

Dear Shabank,

yes, we know it's possible like that.

Then it would be lead to errors in some cases, since usually you use that field to enter the amount.
Some uses may, others not recognize that the amount field is changed after first submit.
Can lead to errors then / maybe missleading.

Thank you for that suggestion,

Th.
rmvanarkel
Posts: 258
Joined: Tue Oct 05, 2010 1:14 pm

Re: Please add another extension point

Post by rmvanarkel »

Isn't it easier to just create a special custom operation for this, see:
https://documentation.cyclos.org/curren ... ml#d5e1958

Or is there a specific reason you want to use the payment functionality. Maybe you can elaborate and give a bit more background on what you are trying to achieve.
admin_de2
Posts: 97
Joined: Wed Dec 31, 1969 9:00 pm

Re: Please add another extension point

Post by admin_de2 »

Dear Roder,

it's like this:
self-printed (not cyclos one's) vouchers are about to transfer from a to b.
the vouchers have different values, ones, twos, fives, tens, etc.

When initiating a transfer, a staff member provides the count of each voucher value as transaction field (ones-field e.g. 3 times, twos-field e.g. 5 times, ..)

Then the transaction-amount is clear: 1 * 3 + 5 * 2 = 13

Next step would be (not clear) that the staff member has to enter the expected amount (since an error may appear counting the vouchers OR calculating the final amount) - this is just for counterchecking.

If the sum matches the count of voucher value types, all is good and the transfer can START.

That means, a transfer status is set to "START".
Next thing is, that the receiving account (voucher-account) has to countercheck the amount and set the transfer status to "END", what means, the same amount is received as sent (in between there are real people who pass on the vouchers - this is why counterchecking as well sending and receiving amounts).

=> I've seen the new wizard thingy. Maybe it's worth looking at it for that.
=> I understand your suggestions so far. I was just thinking about doing it in the transfer mask where all the voucher fields are anyways here to be filled.

Thank you, Thomas
Post Reply