1️⃣: GOOGLE CLOUD SDP (FRONT-END DESKTOP & NATIVE MOBILE) =============================================

📋 ELEMENT DESCRIPTION
--------------------------------
GOOGLE CLOUD SDP (FRONT-END DESKTOP & NATIVE MOBILE) provides a visual element with the REDACT PII (FRONT-END & MOBILE) action to redact personally identifiable information (PII) in text. The front-end element is suitable for applications when reactivity is desired.

🔧 STEP-BY-STEP SETUP
--------------------------------
ℹ️ The steps from 0) to 1) can be automatically performed by logging in into your Google Cloud Console, opening the Cloud Shell (top right corner of your page) and copy pasting this command and press enter:

wget -q https://storage.googleapis.com/bubblegcpdemo/demo-assets/wiseable-gcp-dlp.py && python3 wiseable-gcp-dlp.py

0) Set-up a project from Google Cloud Console:
- Create or select a project
- Enable the CLOUD DATA LOSS PREVENTION (DLP) API for that project
- Create a service account
- Download a private key as JSON.

1) Open the private key JSON file with a text editor, copy/paste the following parameters from your file to the Plugin settings:
- CLIENT_EMAIL
- PROJECT_ID
- PRIVATE_KEY, including the -----BEGIN PRIVATE KEY-----\\n prefix and \\n-----END PRIVATE KEY-----\\n suffix.

2) Register on plugins.wiseable.io. Create a new Credential which associates your BUBBLE APP URL, GCP PROJECT_ID, CLIENT_EMAIL & PRIVATE_KEY.
The registration service will generate your PUBLIC ACCESS KEY. This key serves as a secure proxy for your real API key. It allows your application to communicate with the service without exposing your real API key. Since this PUBLIC ACCESS KEY is explicitly tied to your registered BUBBLE APP URL, it can only be used from that domain, ensuring that even if the key is publicly visible, it remains safe and cannot be misused by unauthorized sources.

3) Enter in the PLUGIN SETTINGS your PUBLIC ACCESS KEY (used for front-end element only).

4) Add the GOOGLE CLOUD SDP (FRONT-END DESKTOP & NATIVE MOBILE) element to the page on which the PII redaction feature must be integrated.

5) Integrate the logic into your application using the following GOOGLE CLOUD SDP (FRONT-END DESKTOP & NATIVE MOBILE) element's states and actions:

EVENTS:
- SUCCESS: Event triggered upon successful redaction
- ERROR: Event triggered upon error

EXPOSED STATES:
Use any element able to show/process the data of interest (such as a Group with a Text field) stored within the result of the following states of the GOOGLE CLOUD SDP (FRONT-END DESKTOP & NATIVE MOBILE) element:
- RESULT: Populated upon SUCCESS event. Contains the redacted text.
- ERROR MESSAGE: Populated upon ERROR event.
- IS PROCESSING: Set to true when processing is in progress, false otherwise.

ELEMENT ACTIONS - TRIGGERED IN WORKFLOW:
- REDACT PII (FRONT-END & MOBILE): Redacts PII in text and populates RESULT state upon completion.

Inputs Fields:
 - TEXT TO ANALYZE: A UTF-8 text string. Each string must contain fewer than 1,000,000 bytes of UTF-8 encoded characters.
 - CHARACTER MASK: Character mask in redacted text (defaults to "*").


2️⃣: REDACT PII (BACK-END)
==========================

📋 ACTION DESCRIPTION
--------------------------------
REDACT PII (BACK-END) redacts personally identifiable information (PII) in text and returns the redacted text. This server-side action provides secure processing for sensitive data.

🔧 STEP-BY-STEP SETUP
--------------------------------
ℹ️ The steps from 0) to 1) can be automatically performed by logging in into your Google Cloud Console, opening the Cloud Shell (top right corner of your page) and copy pasting this command and press enter:

wget -q https://storage.googleapis.com/bubblegcpdemo/demo-assets/wiseable-gcp-dlp.py && python3 wiseable-gcp-dlp.py

Otherwise, follow these manual steps:

0) Set-up a project from Google Cloud Console:
- Create or select a project
- Enable the CLOUD DATA LOSS PREVENTION (DLP) API for that project
- Create a service account
- Download a private key as JSON.

1) Open the private key JSON file with a text editor, copy/paste the following parameters from your file to the Plugin settings:
- CLIENT_EMAIL
- PROJECT_ID
- PRIVATE_KEY, including the -----BEGIN PRIVATE KEY-----\\n prefix and \\n-----END PRIVATE KEY-----\\n suffix.

2) Set up the action "REDACT PII (BACK-END)" in the workflow.
 Inputs Fields:
   - TEXT TO ANALYZE: A UTF-8 text string. Each string must contain fewer than 1,000,000 bytes of UTF-8 encoded characters.
   - CHARACTER MASK: Character mask in redacted text (defaults to "*").
 Output Fields:
   - RESULT: Returns the redacted text.

🔍 IMPLEMENTATION EXAMPLE
======================
Feel free to browse the app editor in the Service URL for an implementation example.

ℹ️ ADDITIONAL INFORMATION
======================
> Detectable PII: https://cloud.google.com/dlp/docs/infotypes-reference

⚠️ TROUBLESHOOTING
================
Any plugin related error will be posted to the Logs tab, "Server logs" section of your App Editor.
Make sure that "Plugin server side output" and "Plugin client side output" is selected in "Show Advanced".

For front-end actions, you can also open your browser's developer console (F12 or Ctrl+Shift+I in most browsers) to view detailed error messages and logs.

Always check the ERROR MESSAGE state of the element and implement error handling using the ERROR event to provide a better user experience.

> Server Logs Details: https://manual.bubble.io/core-resources/bubbles-interface/logs-tab#server-logs

⚡ PERFORMANCE CONSIDERATIONS
===========================

⏱️ BACK-END ACTION START DELAY
-----------------------------------------------
Each time a server-side action is called, Bubble initializes a small virtual machine to execute the action. If the same action is called shortly after, the caching mechanism kicks in, resulting in faster execution on subsequent calls.

A useful workaround is to fire a dummy execution at page load, which pre-warms the Bubble engine for the next few minutes, reducing the impact of cold starts for your users.

Note that for back-end actions, the maximum retrievable result set is capped at 30 seconds duration time - this does not apply to front-end actions.

❓ QUESTIONS?
===========
Contact us at [email protected] for any additional feature you would require or support question.