TreatmentStack.qml

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge remote-tracking branch 'origin/staging' into feature/LDT-3574-misc-sw-enhancements

LDT-3579 Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I - 05: DEV - Feature Implementation

update status colors

  1. … 7 more files in changeset.
LEAHI-APPLICATION-LDT-3574_Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I
LEAHI-APPLICATION-LDT-3574_Misc SW Enhancements - SW - 01 - General Aesthetics - 02-S24 - R&I
add element for status color

add element for status color

LDT-3378: Misc SW Enhancements - SW - 01 - BloodPrime-02 - R&I - 05: DEV - Feature Implementation

- Updated Blood Prime to add submode states for Run and Paused.

- Updated Blood Prime to add Timeout and Countdown to progress.

- Updated Blood Prime commands: removed Increase and Decrease, added Resume.

  1. … 10 more files in changeset.
LEAHI-APPLICATION-LDT-3373_Misc SW Enhancements - SW - 01 - BloodPrime-02 - R&I
LEAHI-APPLICATION-LDT-3373_Misc SW Enhancements - SW - 01 - BloodPrime-02 - R&I
LEAHI-APPLICATION-LDT-3413_HDF - SW - 01 - Main-Tx HDF Tab - Graph - R&I
LEAHI-APPLICATION-LDT-3413_HDF - SW - 01 - Main-Tx HDF Tab - Graph - R&I
LEAHI-APPLICATION-LDT-3393_HDF - SW - 01 - Main-Tx HDF Tab - R&I
LEAHI-APPLICATION-LDT-3393_HDF - SW - 01 - Main-Tx HDF Tab - R&I
Merge branch 'staging' of bitbucket.org:diality-cloud/leahi-application into feature/LDT-3323-enhancements-rinseback-bloodflow

  1. … 10 more files in changeset.
Merge branch 'staging' of bitbucket.org:diality-cloud/leahi-application into feature/LDT-3194-isolated-uf-adjustment

  1. … 2 more files in changeset.
Updated.

Updated.

Add comment for why using * 2 (look & feel)

Add comment for why using * 2 (look & feel)

No longer needed since staging was changed.

No longer needed since staging was changed.

Updated.

Updated.

Updated.

Updated.

User waited too long would follow the same rejected behavior, do we still need to show the specific rejection path for the user waiting too long?

User waited too long would follow the same rejected behavior, do we still need to show the specific rejection path for the user waiting too long?

Updated.

Updated.

Updated.

Updated.

Updated.

Updated.