The Angle parameter requires negative or positive integers, rounded to multiples of 90, to indicate the angle of rotation to be applied:

• Positive values (>45°) define a clockwise rotation.

• Negative values (<-45°) define a counter-clockwise rotation.

• For example, a rotation angle of -90° is equivalent to a rotation angle of 270°.

The Input image parameter must provide the original image via a value resolver whose return value corresponds to the 'action event content' or 'byte array' type.

The Result image parameter defines where the target image should be saved to. The value resolver must define a suitable 'recipient' here (e.g. a variable or an object field) for a 'byte array' or the 'action event content' type.

A common event handling for the two Triggering events 'Rotate Left' (ROTATE_LEFT) and 'Rotate Right' (ROTATE_RIGHT) is created and configured as shown on the right:

• The Validating rule uses Check type to ensure that a 'user' account is present as an input object in the data context of event handling.
  
  ►NOTE◄ Here, the field avatarURL could additionally be checked for 'not empty' with an Entity property rule to ensure that a profile picture was uploaded for this user at all.

The Actions on passed rule is passed are first presented here in an overview. Details per action follow below:

• A Set value event action defines the file path where the user's profile picture can be found as the value of the variable avatarFilePath.
  
  

• Within an If then else event action, the variable rotation is assigned the desired rotation angle (-90° for left rotation, 90° for right rotation).
  
  

• Finally, the event action Rotate image (Event action) follows:
  
  

  • The value for the Angle parameter is taken directly from the variable rotation .
    
    

  • For the Input image and Result image parameters, the text value from the avatarFilePath variable is used as the File path in a File reference value resolver in each case. The read access for the Input image and the write access for the Result image here exceptionally concern the same file. This is therefore overwritten when a rotation is executed.

►NOTE◄ By default, the profile picture does not appear to be visible in the details for the selected user account. The rotated image will not appear until the next time the user in question logs in. Even if the profile picture of the logged-in user is rotated, it does not appear immediately in the top left corner of the user area of the menu bar in the existing session.

►NOTE◄ The rotation overwrites the file referenced in the user account. Nothing changes in the reference in the user account. In this respect, the change takes effect without saving the user account.

The first Set value event action assigns the file path to the profile picture of the user present as input object to the avatarFilePath variable:

• The avatarURL Object property contains a URL that points to the user's profile picture, if one is currently uploaded. Since a relative file path for the server's file system is required instead of the URL, the URL is prepared in two steps by concatenated Replace text value resolvers.
  
  

  • First, the img:// prefix is replaced with the relative path to the server's public directory (in a default installation ./upload/web/).
    
    

  • After that, the parameter part of the URL introduced with a question mark is removed, which enables the Regular expression? option.
    
    

Runtime example:

avatarURL="img://avatar/user_avatar_101.png?c=1619013361517"

... results (correspondingly) ...

avatarFilePath="./upload/web/avatar/user_avatar_101.png"

The following case distinction per If then else event action shall define the rotation angle for either left or right rotation depending on the ribbon button pressed at runtime.

• Within an Entity property rule, this is done by comparing the return value of the value resolver Triggering event with the value of the dynamic enumeration Custom action event (see Static values, 'Any dynamic enumeration'), which defines the 'Rotate Left' event.
  
  

• IF is assumed when the Triggering event is determined as 'Rotate Left', then the variable rotation is assigned the value -90.
  
  

• ELSE is assumed when the Triggering event is 'Rotate Right', since no other triggering events are defined for event handling. Then, without an explicit check (not expanded in the image), the variable rotation is assigned the value 90 for the clockwise rotation.