24 results found

1. Logout trigger

   There's a trigger for login, but there isn't one for logout (as far as I can tell). I would like a trigger on logout as well to perform cleanup of any of the side effects from the login trigger.

   This request is really a result of a separate request that is more important (https://feedback.mongodb.com/forums/923521-realm/suggestions/42102031-decode-user-token) but if there was a trigger for both login and logout it would tie me over until then.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Triggers  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Configure Realm notifications

   Currently only all project owners of the Atlas project in where your Realm app situates will receive notification of suspended trigger. This currently cannot be customized. We want to have the possibility to configure the notifications to include additional emails, not only for project owners.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Triggers  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Add the ability to use a value to reference a database in a trigger

   It would be great if we could use values for the database reference in a trigger, instead of having to select a database from a drop-down.

   An actual use case:

   To be able to use Realm for our various staging areas, we have created multiple Realm apps. One for production, one for UAT, one for test, etc. Each of them pointing to the databases for their respective staging environment.

   We are using Github deployments, and we use a separate branch for each of the staging environments. So when something gets committed to the "deploy-test" branch, it gets to be deployed to the test Realm app. Thanks for adding that feature by the way!

   Now we face the following problem: The database reference is stored in the Github repository. We could work around this, by using values that are not included in the Github repository, but 'manually' added to the Realm app. These values can then be used in the Realm app, and the values can be different per staging environment. This works great for functions, but the problem is that this can't be used for triggers.

   So for now, we're replacing placeholder-values with an actual database name in the staging deployment branches using a script, which is error-prone, and we actually need to do a force-push to make it a bit workable in an automated way. Not something that we're loving at the moment.

   So basically we just one simple thing to have everything work super smooth! So please add the ability to use a value for a database reference in a trigger.

   It would be great if we could use values for the database reference in a trigger, instead of having to select a database from a drop-down.

   An actual use case:

   To be able to use Realm for our various staging areas, we have created multiple Realm apps. One for production, one for UAT, one for test, etc. Each of them pointing to the databases for their respective staging environment.

   We are using Github deployments, and we use a separate branch for each of the staging environments. So when something gets committed to the "deploy-test" branch, it gets to be deployed… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Triggers  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Allow manually disabled trigger to resume without resume token

   I am filing a feature request for the option to: Disable a trigger manually and be able to restart it without using a resume token (i.e. such that DB events that occurred while it was disabled will be ignored by the trigger, and it will simply start listening for new events upon restart).

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   planned  ·  2 comments  ·  Triggers  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close