Hi @GAUTHIERM ,

The above users are used by the application. When you search for the above person_id in the person screen you wont be able to see the records. These IFS_% users will have the person_status as METRIX which is defined in the FSM codes.

 

You can observe these records in the DB level but not through the application. From the person screen the following data constraint is added to filter out the METRIX users. 

<where>
    <data_constraint>
      <constraint>
        <left_operand>person.status</left_operand>
        <operator>NE</operator>
        <right_operand>04</right_operand>
      </constraint>
    </data_constraint>
  </where>

 

Regarding the functionality of the usage of these users, the prefix part of the user will be using the specific user to perform its functions. For an example if a records is created/modified by any mobile related process the created_by/modified_by columns will have IFS_MOBILE. 

Hope this answer helps

Best Regards,
Atheeq

Hi @Atheeq Maharoof, 

Is it possible to have more informations on the triggering of these users / process ?

We would like to understand these process to check there is no impact on our custom process.

For example, our log disapeer regulary and we have detected the connection of IFS_MOBILE user at the same time. There is a link between this two events ?

Best regards and thanks you, 

Gauthier

Hi @GAUTHIERM ,

As per my knowledge, there isn't any connection with the log disappearance and the IFS_MOBILE. The possibilities are,

1. The logs have been already downloaded, so that its not available.
2. The time duration which is mentioned in the server log screen has been elapsed.

Hope this answer helps

Best Regard,
Atheeq

These IFS Internal users were created to facilitate messaging between FSM components - they are all configured with MESSAGE license type.  This avoids the customer’s licensed user counts from being impacted by internal processes.

The IFS_MOBILE person is logged on when the Mobile Service initiates a connection with the FSM  Server.

There is a “Days:” field on the Mobile Log screen from Studio > Tools that determines the number of days of log history that the Mobile logging framework should retain.

@GAUTHIERM 
@Atheeq Maharoof 

Hi Atheeq, 

It must be a coincidence but there is probably another mechanism to extract the server logs. We have noticed that our server logs are disappearing irregularly over 24 hours while no users are downloading them and the hold time is 14 days...

But that’s another subject...