Premium support for our pure JavaScript UI components


Post by Shinya Umeshita »

Hello Bryntum team, This question is about Undo / Redo Process Not Working as expected in salesforce.

The problem ,
The first time we do a Redo Operation , The scheduler does not complete the redo operation only for the first time .
The second redo operation works fine.
Can you investigate the Undo / Redo Proces in salesforce?

Source Code

this.scheduler = window.schedulerpro =
new bryntum.schedulerpro.SchedulerPro({
        project: {
          calendar: this.targetCalendar,
          resourcesData: this.resources,
          eventsData: this.events,
          assignmentsData: this.assignments,
          calendarsData: this.calendars,
          dependenciesData: this.dependencies,
          stm: {
            autoRecord: true
          },
        },

        columns: this.columns,
        startDate: this.startDate,
        endDate: this.endDate,
        rowHeight: 50,
        barMargin: 2,
        viewPreset: this.viewPreset,
        multiEventSelect: true,
	
	tbar: [
          {
            type: 'undoredo',
            items: {
              transactionCombo: null
            },
          },
        ],
    });
Attachments
GIF outside salesforce ENV <br />Works Fine
GIF outside salesforce ENV
Works Fine
BrytumUndoRedo.gif (572.89 KiB) Viewed 483 times
GIF in SalesForce Env<br />The first Redo Is not working fine
GIF in SalesForce Env
The first Redo Is not working fine
SalesforceUndoRedo.gif (687.35 KiB) Viewed 483 times

Post by alex.l »

Hi Shinya Umeshita,

We've reproduced the issue, thank you for your report. Here is a link to the ticket to track the status: https://github.com/bryntum/support/issues/4031

All the best,
Alex


Post by Shinya Umeshita »

Thank you for checking, alex!
I just would like to know what do you suppose when (in what version) you can fix this issue?
Actually I would like to use this feature soon if it is possible.


Post by alex.l »

We can't say exactly now.
We aimed to fix it in one first minor releases of version 5.
The ticket is already marked as premium, so it will be prioritized accordingly. You can track the status using the link I provided above.

All the best,
Alex


Post Reply