Skip to content

Commit d061658

Browse files
committed
refactor: salesforce note style css
1 parent b7a0b67 commit d061658

File tree

1 file changed

+39
-30
lines changed

1 file changed

+39
-30
lines changed

frontend-dev/src/components/AllIntegrations/Salesforce/SalesforceIntegLayout.jsx

Lines changed: 39 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -408,7 +408,7 @@ export default function SalesforceIntegLayout({
408408
)}
409409
<br />
410410
<br />
411-
<Note note={note} />
411+
<Note note={note} maxWidth="900px" />
412412
</>
413413
)
414414
}
@@ -421,37 +421,46 @@ const note = `
421421
<abbr title="International Organization for Standardization">ISO</abbr> 8601 standards.
422422
</p>
423423
424-
<h2>Date Fields</h2>
425-
<p>The recommended format is:</p>
426-
<pre><code>YYYY-MM-DD</code></pre>
427-
<p>For example: <code>2025-09-20</code></p>
424+
<div class="flx" style="align-items: flex-start;">
425+
<div style="flex: -1;">
426+
<h2>Date Fields</h2>
427+
<p>The recommended format is:</p>
428+
<pre><code>YYYY-MM-DD</code></pre>
429+
<p>For example: <code>2025-09-20</code></p>
430+
</div>
428431
429-
<h2>DateTime Fields</h2>
430-
<p>
431-
The recommended formats, which include time and often a timezone indicator, are:
432-
</p>
433-
<pre><code>YYYY-MM-DDThh:mm:ssZ</code></pre>
434-
<pre><code>YYYY-MM-DDThh:mm:ss.sssZ</code></pre>
432+
<div class="ml-2" style="flex: 1; text-align: justify;">
433+
<h2>DateTime Fields</h2>
434+
<p>
435+
The recommended formats, which include time and often a timezone indicator, are:
436+
</p>
437+
<pre><code>YYYY-MM-DDThh:mm:ssZ</code></pre>
438+
<pre><code>YYYY-MM-DDThh:mm:ss.sssZ</code></pre>
435439
436-
<p>
437-
Here, <code>Z</code> indicates Coordinated Universal Time (UTC), and <code>sss</code> represents milliseconds.
438-
</p>
439-
<p>
440-
For example: <code>2025-09-20T10:30:00Z</code> or
441-
<code>2025-09-20T10:30:00.123Z</code>
442-
</p>
443440
444-
<h2>Other Notes</h2>
445-
<p>
446-
While other formats like <code>MM/DD/YYYY</code> might be accepted in certain contexts
447-
(such as <em>Data Loader</em> with specific settings), using the ISO 8601 format
448-
(<code>YYYY-MM-DD</code> for dates and
449-
<code>YYYY-MM-DDThh:mm:ssZ</code> or <code>YYYY-MM-DDThh:mm:ss.sssZ</code> for datetimes)
450-
ensures compatibility and avoids potential issues across various Salesforce APIs and tools.
451-
</p>
441+
<p>
442+
Here, <code>Z</code> indicates Coordinated Universal Time (UTC), and <code>sss</code> represents milliseconds.
443+
</p>
444+
<p>
445+
For example: <code>2025-09-20T10:30:00Z</code> or
446+
<code>2025-09-20T10:30:00.123Z</code>
447+
</p>
448+
</div>
452449
453-
<p>
454-
When working with <strong>REST API queries</strong>, filtering date fields should also adhere
455-
to the <code>YYYY-MM-DD</code> format.
456-
</p>
450+
<div class="ml-2" style="flex: 1; text-align: justify;">
451+
<h2>Other Notes</h2>
452+
<p>
453+
While other formats like <code>MM/DD/YYYY</code> might be accepted in certain contexts
454+
(such as <em>Data Loader</em> with specific settings), using the ISO 8601 format
455+
(<code>YYYY-MM-DD</code> for dates and
456+
<code>YYYY-MM-DDThh:mm:ssZ</code> or <code>YYYY-MM-DDThh:mm:ss.sssZ</code> for datetimes)
457+
ensures compatibility and avoids potential issues across various Salesforce APIs and tools.
458+
</p>
459+
460+
<p>
461+
When working with <strong>REST API queries</strong>, filtering date fields should also adhere
462+
to the <code>YYYY-MM-DD</code> format.
463+
</p>
464+
</div>
465+
</div>
457466
`

0 commit comments

Comments
 (0)