Ned Petrov

Hello,

The scheduler in the new builder is missing the option to set a custom email subject. This is something we are using with the legacy tool and would like to know if there are any plans to implement it in the new one.

Thanks

Hi Salman,

You can use POST /api/v2/users to create a new user.

More details here: https://developer.zendesk.com/api-reference/ticketing/users/users/#create-user 

Ned

Hi PR,

I'm unable to figure out how the “Update Translation” endpoints should be used. Maybe someone else can explain.

What I can suggest is to go over all articles with the API and create a new article with the correct locale for each one, and then delete the one with the wrong locale.

Ned

Hi Erazem,

Are you trying to change the ticket status to solved, by any chance?
You might have a ticket field with the “Required to solve a ticket” checkbox.

Ned

I managed to get it working somehow using the guide here:
https://developerblog.zendesk.com/making-modals-work-in-zaf-v2-251b7c940e58

Here are some snippets from my code as it might be useful to someone:

modal.html___________________
    
        

		
    

Calling the Modal______________
const openFileModal = useCallback(
    async (url: string) => {
        try {
            const client = getZendeskClient()
            const context = await client.context()
            const parent_guid = context.instanceGuid

            const modalContext = await client.invoke("instances.create", {
                location: "modal",
                url: `assets/modal.html#parent_guid=${parent_guid}`,
                size: { width: "80vw", height: "70vh" },
            })

            const modalClient = client.instance(
                modalContext["instances.create"][0].instanceGuid,
            )

            const setHtml = () => {
                const modalContentString = renderToString(
                    fileType === "image" ? (
                        
                    ) : (
                        
                    ),
                )
                modalClient.trigger("drawData", modalContentString)
                client.off("modalReady", setHtml)
            }

            client.on("modalReady", setHtml)
            modalClient.on("modal.close", () => {})
        } catch (error) {
            console.error("Failed to open modal:", error)
        }
    },
    [fileType],
)

Ned

Hi,

I'm experiencing the same issue. Unfortunately, the solution was not shared here.

I have a similar code and everything is working fine, and the modal is getting populated with the expected data, but once I move to a different opened ticket tab and open a modal, the window appears, but it remains empty.

This is the code I'm using to open the modal:

const openFileModal = useCallback(async (url: string) => {
    try {
        const client = getZendeskClient()
        const modalContext = await client.invoke("instances.create", {
            location: "modal",
            url: "assets/modal.html",
            size: { width: "80vw", height: "70vh" },
        })

        const modalClient = client.instance(
            modalContext["instances.create"][0].instanceGuid,
        )

        const setHtml = () => {
            const modalContentString = renderToString(
                fileType === "image" ? (
                    
                ) : (
                    
                ),
            )
            modalClient.trigger("drawData", modalContentString)
            client.off("modalReady", setHtml)
        }

        client.on("modalReady", setHtml)
        modalClient.on("modal.close", () => {})
    } catch (error) {
        console.error("Failed to open modal:", error)
    }
}, [])

Ned

Hi Kevin,

I can successfully create a ticket with the POST /api/v2/tickets endpoint.

Can you please share the request with the json body that gives you the error?

Ned

I tested this and it's working fine with a custom drop-down field using the “POST /api/v2/tickets” endpoint.

I noticed that the beginning of your body is “request” but in the docs it's “ticket”.

{
    "ticket": {
    ....

Hi Jacob,

Is the custom field ID the same in your request and in the error? Just wondering if you have other mandatory custom fields required to open a request. And make sure to put the value tag and not the value you see when viewing the ticket.

For testing purposes, you can try to disable the custom field and see if the request will work without it.

Ned

Hi Vipul,

I think there shouldn't be a difference if the tickets were merged. Can you share an example of the code you're trying to use?

Ned